Bugzilla – Full Text Bug Listing
| Summary: | Dependency resolution from workspace marks pom.xml:s with error "No such directory or file found", if user do not have write access to /tmp/fakerepo | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Tomi Pakarinen <tomi.pakarinen> |
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | igor |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Tomi Pakarinen
This does not provide enough information to troubleshoot the problem. Please provide complete standalone sample project and steps to reproduce the problem. 1. login as root 2. make sure /tmp/fakerepo do not exists already 3. open eclipse 4. create maven projects using m2e test:project-1 test:project-2 5. add dependency from project-2 to test:project-1 6. Login as normal user (without root rights) 7. open eclipse 8. create maven projects using m2e test:project-1 test:project-2 9. add dependency from project-2 to test:project-1 10. now project-2's pom.xml has error "no such directory of file found", because root user owns folder /tmp/fakerepo and normal user do not have rights to it. this does not explain why m2e needs to access /tmp/fakerepo right .. I dug up this a bit. seems that problem is actually in m2e-extras not in core https://github.com/sonatype/m2eclipse-extras/blob/master/org.sonatype.m2e.mavenarchiver/src/org/sonatype/m2e/mavenarchiver/internal/AbstractMavenArchiverConfigurator.java#L640 This is why we always ask for complete standalone example project and steps to reproduce the problem ;-) |