Hi Brett,
Thanks for the suggestion. I may have found the issue. Would it be
this:
Validation Errors:
[DEBUG] For dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped
dependency
must specify an absolute path systemPath.
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped
dependency
must specify an absolute path systemPath.
[DEBUG]
[DEBUG] mypackage:myartifact:jar:1.0.2:compile (selected for
compile)
[DEBUG] Skipping disabled repository central
[DEBUG] myartifact: using locally installed snapshot
[WARNING] POM for 'mypackage:myartifact:pom:1.0.2-SNAPSHOT:test' is
invalid.
Its dependencies (if any) will NOT be available to the current
build.
[DEBUG] Reason: Failed to validate POM for project
mypackage:myartifact at Artifact
[mypackage:myartifact:pom:1.0.2-SNAPSHOT:test]
[DEBUG]
Validation Errors:
[DEBUG] For dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped
dependency
must specify an absolute path systemPath.
[DEBUG] For dependency Dependency {groupId=weblogic,
artifactId=webservices, version=10.0, type=jar}: system-scoped
dependency must specify an absolute path systemPath.
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped
dependency
must specify an absolute path systemPath.
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=webservices, version=10.0, type=jar}: system-scoped
dependency must specify an absolute path systemPath.
[DEBUG]
Now in this project, we are inheriting from a parent POM
(standardised
for our department) with entries like this:
(WL_HOME is Weblogic install directory)
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.5.0.11</version>
<scope>system</scope>
<systemPath>${java.home}/../lib/tools.jar</systemPath>
</dependency>
<dependency>
<groupId>com.sun</groupId>
<artifactId>rt</artifactId>
<version>1.5.0.11</version>
<scope>system</scope>
<systemPath>${java.home}/lib/rt.jar</systemPath>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>weblogic</artifactId>
<version>10.0</version>
<scope>system</scope>
<systemPath>${env.WL_HOME}/server/lib/weblogic.jar</
systemPath>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>webservices</artifactId>
<version>10.0</version>
<scope>system</scope>
<systemPath>${env.WL_HOME}/server/lib/webservices.jar</
systemPath>
</dependency>
Now it only fails on the Weblogic related entries. With the Java
system dependencies it seems to do fine.
Has the handling of this changed from 2.0.* to 2.2.*?
If so, what should we replace it with?
And will these settings also work for people still using maven
2.0.10?
Ellecer
On Fri, Nov 20, 2009 at 1:01 PM, Brett Randall <[email protected]>
wrote:
Hi Ellecer
What is the output of mvn -e -X ...
Brett
On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia <[email protected]
wrote:
Hi,
How come when I try a build using Maven 2.2.1 I get multiple
messages
like
this:
"[WARNING] POM for 'mypackage.artifact:pom:1.0.2-
SNAPSHOT:compile' is
invalid.
Its dependencies (if any) will NOT be available to the current
build."
These errors weren't displaying when I was using Maven 2.0.10
I'm trying to use the newer version of Maven but I can't proceed
with
these error messages.
How can I find out what are the actual errors it's referring to? I
didn't come across any mention of relevant POM format changes
going
from Maven 2.0.* to 2.1.* or 2.2.* - if anyone has any info on
this it
would be a great help! Is there a way to validate the pom and get
format error details from Maven?
thanks,
Ellecer
---
------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---
------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
