Community
Participate
Working Groups
Build Identifier: I20110613-1736 Lots of these errors in the error log (with debug enabled): <quote> eclipse.buildId=I20110613-1736 java.version=1.6.0_26 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 -debug -clean Error Sun Aug 14 22:40:49 PDT 2011 File outside of project is being compiled: FileName.java </quote> This is the complete "Error Details" content. There are lots of these errors each time build happens listing many files that are in reality safely asleep very much inside project source directories. in the end build fails with an NPE logged in as a separate bug. Reproducible: Always
Are the files that get reported in any way special? Are they generated?
nothing special about the files - they are from various real source folders and contain rather mundane code - most of them are .java and a couple are .aj
one more little thing - I have just downloaded eclipse-SDK-3.6.2-linux-gtk-x86_64.tar.gz (eclipse.buildId=M20100211-1343) and the same project builds just fine.
so is this still an issue for you? Was the other eclipse version 3.7?
Yes the bug occurred on 3.7, I will be using 3.6 for now so I am not blocked on it. But will be happy to switch back to 3.7. One thing I may need to clarify - the files are nothing special - just not the default "src" - all the sources in the project are in all kinds of folders - I am using eclipse on top of existing non-ide project structure. It is true though that the files that are named in the errors are no different from other files residing in same directories.
We just can't seem to recreate this issue. Are you able to share the project with me? (privately?) Failing that, can you maybe let us see your .classpath file so we can look for something unusual in it? thanks.
I would not be able to send you the whole project. Sadly, it would not even help anymore :( I have just switched back to 3.7 to make sure I can still reproduce it and I can't. My bad for not saving a snapshot earlier. BUT - after I installed 3.6 - the project was ok there and I have fixed up all the compile problems and rushed on with work (deadlines you know). So I have just reopened it in 3.7 to make sure I can reproduce it still and it's NOT there. I will try to recreate the situation after I have more progress to show to my employer. as far as the .classpath file - I did look at it and there was nothing to distinguish it from another (from a similar project that did not have a problem).
Hi there, I encountered the same error in indigo SR1, switching back to 3.6.2 (using my original workspace, see below) did not help, neither using the ajdt development build (2.2.0) - the NPE Yuriy filed in the other bugreport got resolved there, but not the original problem. What "solved" the issue was using a new, empty workspace and checking out all projects again - now it works even in 3.7.1 (still using ajdt 2.2.0, but i guess the stable build would work, too).
