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
Priority: Critical
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]
