Bugzilla – Full Text Bug Listing
| Summary: | Case typo on dependency prevents dependency being resolved when typo fixed | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Neale Upstone <neale> |
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | igor, mkleint |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
Can you confirm the problem still exists in m2e 1.0 but not maven 3.0.3 on command line? Sorry. I don't have either installed, and don't intend to for the moment. in any case it's most likely an issue with maven itself. Closing old/stale bugreports. |
Version: 0.12.1 (as included in Spring Tool Suite 2.7.0) There is some case sensitivity that is not being handled well. Under Windows, if I try to incorrectly get this dependency: <dependency> <groupId>net.liftweb</groupId> <artifactId>lift-mapper_2.9.0-1</artifactId> <version>2.4-m1</version> <scope>compile</scope> </dependency> then a directory named 2.4-m1 is created in the relevant place on the file system recording that the artifact was not found at various repositories. If I think correct 2.4-m1 to 2.4-M1, the artifact is still not resolved. If I delete the directory named 2.4-m1, and try again, all works, with 2.4-M1 being created.