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 108019 [details] A POM that exhibits the described issues. NetBeans 6.9.1 correctly interrogates my pom.xml and loads 85 dependent jars and their requisite dependencies as well. NetBeans 7 only loads 80, several of which are fairly shallow dependencies (like the bean loader for spring-core). Things work if you explicitly define them in the POM, but otherwise libraries like common-management-1.0.jar (a direct dependency of camel-core) do not appear. I'm running 6.9.1 side-by-side with NetBeans 7, and 6.9.1 loads the classpath correctly.
After I refreshed the index from the options screen, maven tab, I was able to resolve the dependencies that it could not find before.
Removed any unnecessary repositories and re-indexed the remaining Maven repos twice, just to be safe. Performed a mvn clean & build on the project, then re-loaded the project within NB7. No luck - still missing dependencies. Rebuit the parent as well as the individual child modules, but that didn't appear to make a difference. Performed a "Build with Dependencies," but no luck. Closed the project, re-opened it... still missing deps. Re-loaded the IDE, still missing deps. Seems like the re-indexing didn't help out with my scenario. Does anything else modify NB7's dependency resolution?
I subsequently went whole-hog and deleted ~/.netbeans/7.0/, starting from scratch. Made sure I had a blank slate. Same issues. Re-indexed again after deleting the user directory. Issues remained. _Then_ I switched to Maven 2.2.1 and things started working again! Didn't have to re-index, either. So it seems this has to do with either Maven 3 or the bundled implementation.
I was not able to reproduce in a dev build. commons-management-1.0.jar (org.fusesource.commonman) appeared under Dependencies after I built and opened your project. Double checked in 7.0 FCS with a fresh user dir; same result. (To make the attachment buildable, I had to comment out the <parent> declaration, replacing with <version>3.5</version>; it still of course failed during the make-assembly goal since you did not attach a complete project, just a POM.) Also compared the Dependencies listing to Libraries in 6.9 and did not notice any difference. The Maven indices should not be involved in dependency resolution, and the NB user dir is unlikely to matter either. Something broken in your local repository might be responsible. Or the parent project might be affecting how this project is loaded (but I cannot see that so I do not know).
Might be fixed in dev build then. The workaround for me was to use Maven 2.2, as the built-in Maven 3 implementation always missed the same dependencies while my Maven 2.2 installation always fetched them. I don't necessarily think the index or the user dir was the fix, but instead the difference between the Maven 2 libraries and the Maven 3 libraries.
(In reply to comment #5) > The workaround for me was to use Maven 2.2, > as the built-in Maven 3 implementation always missed the same dependencies > while my Maven 2.2 installation always fetched them. Maven builds in NB 7.0 run an unmodified Maven 3.0.3 binary, so it is possible you are simply running into an M3 upgrade issue. https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html has a list of things you should look over. Generally speaking, M3 is just stricter about practices that were discouraged under M2 as well.
Created attachment 109066 [details] Better test case (uses a site which gives proper 404s)
Comment on attachment 109066 [details] Better test case (uses a site which gives proper 404s) Oops, wrong issue, please ignore.
I use NetBeans 7.0.1 with Maven 2.2.1 NetBeans 6.9 works perfect, but 7.0... I have a complex POM and jars of some dependencies are not displayed in "Dependencies" branch of the "Projects" window. Probably as a result inline syntax analizer gives me a lot of syntax errors like "package xxx does not exist" - despite compilation works without any problem. Just due to this wrong syntax analizing still can't migrate to 7.0 I have problems with the following dependencies: <dependency> <groupId>com.scc.slm</groupId> <artifactId>publicInterface</artifactId> <version>${project.version}</version> </dependency> - this is my own sub-project. It is not displayed in the "Dependencies" at all. <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <scope>system</scope> <version>1.6</version> <systemPath>${java.home}/../lib/tools.jar</systemPath> </dependency> it is displayed as "tools-1.6.jar" (old NetBeans displays it as "tools.jar"), and displays a warning: "Dependency not loaded yet. Build project to correct errors."
(In reply to comment #9) > this is my own sub-project I cannot evaluate without a complete, self-contained test case. > it is displayed as "tools-1.6.jar" (old NetBeans displays it as "tools.jar"), > and displays a warning: "Dependency not loaded yet. Build project to correct > errors." Working fine for me in a 7.1 development build. (I filed bug #203613 but it is something else.) If you continue to have issues with 7.1, please file fresh bugs with complete steps to reproduce from scratch.
It really works in 7.1 beta ! 7.0 has the problem only - since RC1.
Same issue for NetBeans 7.3. We are using Eclipse in our project. I tried to validate NetBeans 7.3 as an alternative to Eclipse. But when I build our maven project with NetBeans 7.3, there is always one dependency NetBeans cannot resolve. I will take a look on the next NetBeans release. But for now im back using Eclipse again, sorry.
hansgeorg.schwibbe: please do not move the Version field forward. And bugs like this can only be addressed if you can provide a test case for developers to reproduce.
hansgeorg.schwibbe: please provide a testcase project and reopen the issue thanks. Without it we cannot evaluate your problem. Are you using maven 3.x to build your projects or 2.x?
I am using Maven 3.0.4 with Sonatype Nexus 1.9.2.4 as repository. I cannot provide a sample project because it is not open source.
(In reply to comment #16) > I am using Maven 3.0.4 with Sonatype Nexus 1.9.2.4 as repository. I cannot > provide a sample project because it is not open source. ok, and can you provide some information about the dependency? is it transitive or direct? are the coordinates from a public repository? is it a system dependency? is it managed? etc.. can you paste the definition of the dependency? are some system property expressions used in the definition?