Community
Participate
Working Groups
Today, I suddenly got this error: The project was not built since its build path is incomplete. I actually know what I did - I updated to Ubuntu 11.10 - but that should have no influence on Eclipse or Maven or Java (I use my own version, not the one supplied by the OS). To make sure, I checked and I found that someone (= not me or my scripts) adds "-vm /usr/bin/java" to the startup parameters even when I specify a different JDK in eclipse.ini or via JAVA_HOME. Okay, I fixed that and now, the correct VM is used. But the error doesn't go away. The class mentioned in the error is in the classpath (I can locate it with CTRL+SHIF+T). Workspace layout: Project A (closed) Project B (depends on A, open) Project C (depends on A and B, open) Project B builds without problems. Project C is stuck. I tried: - Open/close project C - Maven -> Update dependencies... - Maven -> Update Project Configuration... - Editing and saving the POM - Compiling Project A from the command line and refreshing the workspace - Editing the parent POM of the three projects All with no avail. As it is right now, I have to keep project A open. This is frustrating. The new code to handle dependencies in 1.0.100 is pretty unstable.
Update: Opening project A solves the build path problem but I still get compile errors in code from project C that depends on code from project A. In "Maven Dependencies", I can see project A as a workspace dependency (not as a JAR file). If I open the source code for such an error, I see the usual "XYZ cannot be resolved to a type". If I select "XYZ" and press F3, the Java source file for XYZ is opened. I'm not able to provide a test case for you since it's an unstable behavior. I have broken and working objects in the same workspace. Is there some cache file or something that I can delete? Or anything else that I can try to debug this further? Logging options?
Just in case: I'm using the 3.0.3 embedded Maven (not the 3.0.2 which comes with 1.0.100)
(In reply to comment #0) > Today, I suddenly got this error: The project was not built since its build > path is incomplete. > > I actually know what I did - I updated to Ubuntu 11.10 - but that should have > no influence on Eclipse or Maven or Java (I use my own version, not the one > supplied by the OS). > > To make sure, I checked and I found that someone (= not me or my scripts) adds > "-vm /usr/bin/java" to the startup parameters even when I specify a different > JDK in eclipse.ini or via JAVA_HOME. > > Okay, I fixed that and now, the correct VM is used. But the error doesn't go > away. Not sure why this was a problem but in Eclipse you may want to verify the Installed JREs (Window > Preferences > Java > Installed JRE).
Workspace resolution state is cached in .metadata/.plugins/org.eclipse.m2e.core/workspaceState.ser. You can configure log level details in .metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.<m2e-version>.xml file, but I am not sure dependency resolution logic was instrumented with enough logging (patches are welcome!). We are not aware of *any* stability problems or any other issues with dependency resolution implementation in m2e 1.0 (well, apart from classified dependencies, but lets pretend this is a feature ;-) ). I am very interested to know what triggers the problem and/or a sample project with steps to reproduce it.
I have updated to SR1 (Indigo 3.7.1) and no problems since then. I saw that there is a 1.0.200 release and even a 1.1 on the m2e update site. Are thise official releases? Is it safe to upgrade?
Closing as per the last comment. 1.1 is going to be m2e next release planned for the next year. It should be safe to upgrade to the current 1.1 builds, but as with anything work-in-progress proceed with caution.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
