Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 2.0.4, 2.0.5
-
Fix Version/s: None
-
Component/s: Bootstrap & Build
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
In a plugin pom.xml,
<dependency>
<groupId>weblogic</groupId>
<artifactId>weblogic</artifactId>
<version>[9.0,)</version>
<scope>system</scope>
<systemPath>${wl.home}/server/lib/weblogic.jar</systemPath>
</dependency>
In ~/.m2/setting.xml,
<settings>
<profiles>
<profile>
<id>weblogicConfig</id>
<activation>
<activeByDefault/>
</activation>
<properties>
<wl.home>c:/java/bea-9.2/weblogic92</wl.home>
</properties>
</profile>
</profiles>
<activeProfiles>
<activeProfile>weblogicConfig</activeProfile>
</activeProfiles>
</settings>
When build the plugin, it works fine.
In a project that uses this plugin, when build, it causes the following error:
Project ID: org.codehaus.mojo:weblogic-maven-plugin
POM Location: Artifact [org.codehaus.mojo:weblogic-maven-plugin:pom:2.9.0-SNAPSHOT]
Validation Messages:
[0] For dependency Dependency {groupId=weblogic, artifactId=weblogic, version=[9.0,), type=jar}: system-scoped dependency must specify an absolute path systemPath.
Issue Links
| This issue duplicates: | ||||
| MNG-2626 | System scope dependencies in parent POM cause validation warnings for most plugins and errors in assembly plugin |
|
|
|
The same problem exists for system dependencies defined in a non-plugin pom.xml.
Would someone please provide a fix for this? It's preventing me from doing what I need to do in my build, and I don't see any workarounds to the bug.