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:
[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)
Is this "Working As Designed"?
Is this the correct way to approach this, or what don't I know about yet??!
Is there a way to get this to work as I am trying to (e.g. a ${} variable
available to use in the modules dependency <systemPath>)?
Also, Is there a page that lists all of the available ${} variables? I
could not find one...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
