Bugzilla – Full Text Bug Listing
| Summary: | MavenDependencies classpath container is empty if single <dependency/> element is invalid | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Igor Fedorenko <igor> |
| Component: | m2e | Assignee: | Igor Fedorenko <igor> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david, filippo.rossoni |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | 369742 | ||
| Bug Blocks: | |||
Opened bugreport against Maven core http://jira.codehaus.org/browse/MNG-5073 *** Bug 371429 has been marked as a duplicate of this bug. *** Implemented. http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=9c7d64c5d7d53480b12d6b06eaad966492cb3355 https://github.com/sonatype/m2e-core-tests/commit/acdd35c1f542e76ef690da9c5759d989895c1175 |
As a user, I expect m2e to populate Maven Dependencies classpath container with known/resolved dependencies even if some dependencies cannot be resolved or have incomplete <dependency/> element in pom.xml. For example, for pom.xml below, I expect to to see slf4j dependency even though junit dependency is missing required <version/> element. <project> <modelVersion>4.0.0</modelVersion> <groupId>xxx</groupId> <artifactId>m01</artifactId> <version>0.0.1-SNAPSHOT</version> <dependencies> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.6.1</version> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> </dependency> </dependencies> </project>