This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 102318 [details] Patch that was built in the IDE while doing these tests - should not affect the result from the ClassPath, to my knowledge. [custom build from 25743d95d6de, with a custom patch for SourceForBinaryQuery, will be attached] While trying to reproduce bug #188323: I have a checkout of: http://svn.apache.org/repos/asf/maven/maven-3/trunk revision 960018. It has been built before, so various generated sources exist. When I did: 1. rm ~/.m2 2. start with clean userdir 3. open the "trunk", wait until the project is recognized, scanned. 4. open required projects 5. build "trunk" 6. On each project, from top, resolve problems As a result, there are compilation errors in Maven Compat, DefaultRepositoryMetadataManager, claiming that org.apache.maven.artifact.repository.metadata.io.xpp3.MetadataXpp3Reader cannot be found. Looking at the compile classpath of the DRMM, it really does not refer to maven-repository-metadata-3.0-SNAPSHOT.jar (and so the compilation errors are correct from the parser's point of view). The CP does not change after restart and deleting ${userdir}/var/cache. I am attaching a screenshot and list of all classpath (maven-188323-bad-cp.png and maven-188323-bad-cp.txt respectivelly), as returned after second IDE restart. When I did not do step "5" (starting again with a clean userdir and deleting .m2), there are no compilation errors for any of the projects and the compilation classpath is different (maven-188323-good-cp.txt). (Note that the results may be non-deterministic - I was performing similar steps many times, and the results were not always consistent or predictable.)
Created attachment 102319 [details] Screenshot from IDE when the compile CP appears to be broken.
Created attachment 102320 [details] "Bad" CP listings
Created attachment 102321 [details] "Good" CP.
Using a recent (from yesterday) build, I see another problem with source path: after building the maven project, the source path for e.g. maven-model/src/main/java/org/apache/maven/model/merge/ModelMerger.java is: /space/maven/trunk/maven-compat/src/main/java /space/maven/trunk/maven-compat/src/main/scala /space/maven/trunk/maven-compat/src/main/groovy /space/maven/trunk/maven-compat/src/main/resources which is wrong, it should also contain: maven-model/target/generated-sources/modello The classpath for this folder is (seems to be) the same as above and does not contain the folder itself, causing further problems. After restart, the sourcepath is correct. This is on: Path: . URL: http://svn.apache.org/repos/asf/maven/maven-3/trunk Repository Root: http://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 1074467 Node Kind: directory Schedule: normal Last Changed Author: bentmann Last Changed Rev: 1074306 Last Changed Date: 2011-02-24 22:31:36 +0100 (Thu, 24 Feb 2011)
Did I get the summary right?
Observed with https://github.com/hudson/hudson.git projects: open root and prime; open hudson-core and prime, which is successful. "Generated Sources (localized)" appears in logical view yet various source files are marked as erroneous due to missing Messages, even though Messages.java in fact exist. Metadata inspector confirms that sourcepath for src/main/java/ is missing target/generated-sources/*/ entries. Fixed by IDE restart.
(In reply to comment #6) > Observed with https://github.com/hudson/hudson.git projects: open root and > prime; open hudson-core and prime, which is successful. "Generated Sources > (localized)" appears in logical view yet various source files are marked as > erroneous due to missing Messages, even though Messages.java in fact exist. > Metadata inspector confirms that sourcepath for src/main/java/ is missing > target/generated-sources/*/ entries. Fixed by IDE restart. trying almost the same but building instead of priming, results in correct behaviour for me. I've tried the jenkins repo instead of hudson (had that one checked out already). clean vs build actions seemed to add/remove the error markers correctly, however it took a hell of time get fully updated, the project is rather big.
same with maven-model, clean vs. build adds/removes error marks in files correctly (after a while)
core-main #2b662d595857
Integrated into 'main-golden', will be available in build *201204110400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/2b662d595857 User: Jesse Glick <jglick@netbeans.org> Log: #190852: Maven sourcepath missing newly created gensrc roots
Integrated into 'main-golden', will be available in build *201204120400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/2b662d595857 User: Jesse Glick <jglick@netbeans.org> Log: #190852: Maven sourcepath missing newly created gensrc roots
*** Bug 191518 has been marked as a duplicate of this bug. ***