Compiles fail on 1035-1080
I can't get my code to compile with 1080 (or 1035). The analysis says
that it is correct code, but when I compile my code, it can't find
classes even in the same package. I gather this is a configuration
problem but it appears to be an incosistency between the analysis and
the compilation.
Any one else experience this or have a suggestion around it?
Thanks,
Dave Forslund
Please sign in to leave a comment.
I had that problem too, using Jikes, but for some reason switching to javac fixed it. I haven't had time to look into it more however.
I had exactly the same problem. The solution : Go into the build menu and click on make Project... Then you will be able to use compile again !
I guess this has something to do with class cache... but once the make is done I didn't have to do it again up to now.
Hope it will work for you too.
Nicolas.
OK. I don't understand why this has to be done? Doesn't it determine
the dependencies and compile what needs to be compiled? I have some
classes in my directories that don't have the necessary support
libraries (I filter tham out when I do an ant build), but I don't see
how do do this with IntelliJ.
Why is this behavior this way on Aurora? I've filed a bug on this.
Unfortunately, I just did the entire compile of the project and then
tried to compile one of the files individually and still get the same
error. It says that one of my packages isn't there and can't do the
import (even though the analysis works fine).
Thanks,
Dave
frank wrote:
It doesn't fix it for me, either.
I think I understand the problem but not how to correct it. I can
compile my project by telling it to build everything. However,
selecting an individual file to compile fails with any imported
class including one in the same package. I think it is not seeing
where it compiles the .class files to when I compile a single file.
This is almost surely a configuration problem. In earlier versions
I could specify the output directory of the compiler, but can't find
that in this version of IDEA. How is this configured?
Thanks,
Dave
David Forslund wrote:
>> I had exactly the same problem. The solution : Go into the build menu
>> and click on make Project... Then you will be able to use compile again !
>> I guess this has something to do with class cache... but once the make
>> is done I didn't have to do it again up to now.
>>
>> Hope it will work for you too.
>>
>> Nicolas.
I am having the exact same problem with build 1071. The only way I've got around it is to compile first using jEdit, then the IDEA compile works fine.
I figured out what is happening. Apparently you have to have a full
successful compile of the project to get any classes to compile
correctly. I had compiled the entire project and observed that
some classes didn't compile (some intentionally missing libraries).
However, there was nothing in the output directory. Today I
excluded the files that wouldn't compile and, voila, the output
directory now is populated! Now it will compile individual classes
without any problems. I don't understand why this behavior has changed
from the earlier version, but at least it know works.
There is a problem in that it isn't compiling all my classes, but
at least I can compile them on demand now.
Dave
David Forslund wrote:
>> OK. I don't understand why this has to be done? Doesn't it
>> determine the dependencies and compile what needs to be compiled? I
>> have some
>> classes in my directories that don't have the necessary support
>> libraries (I filter tham out when I do an ant build), but I don't see
>> how do do this with IntelliJ.
>>
>> Why is this behavior this way on Aurora? I've filed a bug on this.
>>
>> Unfortunately, I just did the entire compile of the project and then
>> tried to compile one of the files individually and still get the same
>> error. It says that one of my packages isn't there and can't do the
>> import (even though the analysis works fine).
>>
>> Thanks,
>>
>> Dave
>> frank wrote:
>>
>>> I had exactly the same problem. The solution : Go into the build menu
>>> and click on make Project... Then you will be able to use compile
>>> again !
>>> I guess this has something to do with class cache... but once the
>>> make is done I didn't have to do it again up to now.
>>>
>>> Hope it will work for you too.
>>>
>>> Nicolas.
>>
>>
>>