Bugzilla – Full Text Bug Listing
| Summary: | POM editor does not show scope inherited from dependency management | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Tobias Oberlies <t-oberlies> |
| Component: | m2e | Assignee: | Milos Kleint <mkleint> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | mkleint |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
I just found out that it is possible to change the default scope of a dependency through dependency management, e.g. <dependencyManagement> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.8.2</version> <scope>test</scope> </dependency> </dependencies> </dependencyManagement> If a child POM then only specifies a simple depencency, e.g. <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> </dependency> the POM editor correctly displays the inherited version, but it does not seem to be aware of the inherited scope. The Dependency Properties dialog shows the incorrect scope "compile". It should display the correct inherited scope. Also, in the dependencies list, it would be great if the managed scope could be shown in case it is not "compile".