[ http://jira.codehaus.org/browse/MNG-1471?page=comments#action_52888 ]
John Casey commented on MNG-1471: --------------------------------- You have your third party libraries in SCM, and it's been decided that this should remain the case...how would this preclude your using an SCM-based Maven repository? As I mentioned in my comment to Matthew on 05-Dec, the Maven-Wagon project does have an SCM provider (not sure what the status of it is, though). This, along with a custom artifact repository layout (to adapt to non-m2-ish layout of your /lib), should enable you to resolve those libraries without any custom design on the part of Maven. While this practice has not been fully realized yet, there is nothing tying users to the default Maven 2.x repository layout for their own repository instances; you only need to have an appropriate ArtifactRepositoryLayout and the right wagon provider in place. These two tasks are still non-trivial, but possible with the current implementation. Would this solve your problem? Would there be any problem with checking in POMs for those third party libraries, to help make transitive dependencies possible for those? If not, it's still possible to use them. > Module paths for system scope are relative to parent pom instead of its own > --------------------------------------------------------------------------- > > Key: MNG-1471 > URL: http://jira.codehaus.org/browse/MNG-1471 > Project: Maven 2 > Type: Bug > Components: maven-compiler-plugin > Versions: 2.0 > Environment: Win XP, Maven 2.0 > Reporter: Jeff Jensen > Assignee: John Casey > Priority: Critical > Fix For: 2.0.1 > Attachments: MNG-1471-maven-project.patch > > Original Estimate: 30 minutes > Remaining: 30 minutes > > When building from the parent POM dir, all paths are relative to it. A > problem occurs when its modules have dependencies of <scope>system</scope> - > the module's corresponding <systemPath> is relative to the parent POM dir, > instead of the module's POM dir. > With a module's <systemPath> set to compile correctly it on its own, > compiling from its parent POM dir gives this error: > [ERROR] BUILD ERROR > [INFO] > ---------------------------------------------------------------------------- > [INFO] Failed to resolve artifact. > GroupId: thegrp > ArtifactId: subsystem > Version: 2.1-SNAPSHOT > Reason: System artifact: thegrp:subsystem:jar:2.1-SNAPSHOT not found in > path: src\lib\subsystem.jar > thegrp:subsystem:2.1-SNAPSHOT:jar > (would be nice to have the fully qualified path name listed there, instead of > the relative one so users would know where it is really looking for it > from) > Expected behavior is that Maven treats system scope paths relative to the > module POM, not the parent's POM. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
