| Summary: | XML Editor allows managed dependency with no version | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Matthew Piggott <matthew> |
| 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 7 | ||
| Whiteboard: | |||
|
Description
Matthew Piggott
not sure I understand the problem. can you give steps to reproduce? this could be related to https://issues.sonatype.org/browse/MNGECLIPSE-2636 in the sense that our project loading might swallow the warning emitted by maven (if there is any) Sorry, I think I had a description of the setup in another bug. Create a project and a module, add a dependency into the module then manage a dependency in the project and remove the version element. At this point there should be a build error in the module but no problems marked in the project. Add a version to the dependency in the module, and a warning marker is added for overriding version null. http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=f59b86b5b44a0d2ada42f5fc35edc5817a785782 fixes the part of editor warning marker appearing for version null. The missing marker for missing PM version is likely a consequence of us reading the maven model with no validation.. in that sense this part is duplicate of #350466 |