[ http://jira.codehaus.org/browse/MNG-1471?page=comments#action_52803 ]
Matthew Wheaton commented on MNG-1471: -------------------------------------- f they take systemPath away, as he says, then that'll break me again, for sure. I'm really contemplating NOT using M2. In any case, my workaround to make it truly dynamic, is my build.bat file first calls an ANT script that compiles a DependencyBuilder class that I created, which iterates through the jar files in my "lib" directory, and creates a string that has all the <dependency> entries in it. Then, I have a pom that lives in my "lib" project called pom-template.xml, that, while still in ANT, I copy to the same directory renaming to pom.xml. I filter the file using the ANT filter mechanism to ADD the string I just created in the DependencyBuilder class, giving a psuedo-dynamic discovery of dependencies. Then, I reference the "libs" project in each of the sub-projects. A little complicated, but then I don't have to manually add JARs to the build when the developers add 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]
