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.
| Summary: | Incorrect dependency graph shown in certain cases involving deep transitivity | ||
|---|---|---|---|
| Product: | projects | Reporter: | Jesse Glick <jglick> |
| Component: | Maven | Assignee: | Tomas Stupka <tstupka> |
| Status: | REOPENED --- | ||
| Severity: | normal | CC: | anebuzelsky, theanuradha |
| Priority: | P3 | ||
| Version: | 7.0 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | DEFECT | Exception Reporter: | |
|
Description
Jesse Glick
2010-11-01 19:23:29 UTC
e259066c6846 (NbRepositorySystem) apparently working toward this. Easiest fix would be to follow http://svn.apache.org/viewvc?view=revision&revision=1348663 but since we can have a hard dep on M3/Aether this could likely be inlined & simplified. simple upgrading to dependency-tree 2.0 didn't cut it in the graph view. the dependency:tree goal shows the batik-js node correctly.. interestingly dependency:tree in version 2.5 is using the DependencyGraphBuilder component, not DependencyTreeBuilder. Needs deeper rewrite, also MavenProject.getProjectBuildingRequest() is being used by the component, thus the base project's MavenProject instance cannot be used here. a side note: the batik-js is not only missing in the graph, but also in the list of dependencies for artifacts in local repository. only batik-script contains it (the one really defining it) contains it in the list. apparently there's something we also do wrong when creating the dependencies list. This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss Reopen |