Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
Hi Ellecer,
Just scanning through this thread I'm not sure if anyone has asked you to
run mvn help:effective-pom in the problem environment. Does that show the
correct variable substitution?
Brett
On Tue, Nov 24, 2009 at 5:39 PM, Ellecer Valencia elle...@gmail.com wrote:
Hi Other Brett,
It's a similar problem, except that the environment settings are
coming from the shell environment and not a setttings.xml
Ellecer
On Mon, Nov 23, 2009 at 6:16 PM, Brett Randall javabr...@gmail.com
wrote:
Hi Ellecer,
Is there a chance you are seeing
http://jira.codehaus.org/browse/MNG-4148 ,
which is duplicated by http://jira.codehaus.org/browse/MNG-2626 ? Does
that
fit your parent POM hierarchy?
Other Brett
On Mon, Nov 23, 2009 at 2:17 PM, Ellecer Valencia elle...@gmail.com
wrote:
On Mon, Nov 23, 2009 at 11:18 AM, Brett Porter br...@apache.org
wrote:
Did you also export WL_HOME?
I tried something similar here and it works fine in 2.2.1.
- Brett
Hi Brett,
I'd presume the environment variable being there means that's already
happened. =)
This entry is in .bashrc so I'm pretty sure the environment var is
always created.
export WL_HOME=/usr/java/weblogic
I've just created a new session window and see these errors when I run
with mvn -o -X -e package
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.
Ellecer
On 23/11/2009, at 10:08 AM, Ellecer Valencia wrote:
But that's exactly the problem - it *is* defined in the environment.
:(
$ls -l $WL_HOME/server/lib/webservices.jar
-rwxr-xr-x. 1 dev dev 1696324 2009-10-30 16:55
/usr/java/weblogic/server/lib/webservices.jar
$echo $WL_HOME
/usr/java/weblogic
The Maven project I am trying to build has a pom.xml with a parent
pom
parent
artifactIdsuper_pom/artifactId
groupIdmypackage/groupId
version1.0.2-SNAPSHOT/version
/parent
and it's in super_pom where the weblogic dependency is declared.
On Mon, Nov 23, 2009 at 9:18 AM, Brian Fox bri...@infinity.nu
wrote:
Well Maven sees it just like the message:
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped
dependency
must specify an absolute path systemPath.
So since the first one works and the second one doesn't, that leads
me
to believe that WL_HOME isn't defined in your environment.
On Sun, Nov 22, 2009 at 9:06 AM, Ellecer Valencia
elle...@gmail.com
wrote:
Hi Brian,
Could you please clarify what's actually plain wrong about it?
Going back to the example I posted:
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
Do you mean the first one, referencing ${java.home} is correct
and
the one referencing ${env.WL_HOME} is wrong? So what should we do
to
make it work?
thanks,
Ellecer
On Sat, Nov 21, 2009 at 4:33 AM, Brian E. Fox bri...@infinity.nu
wrote:
Maybe 2.2.2 will fix it. =)
Not likely. The pom is plain wrong an it was a bug in 2.x which
allowed it
to go unnoticed.
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall
javabr...@gmail.com
wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team
log
that
:).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia
elle...@gmail.com
wrote:
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
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
Hi Other Brett,
It's a similar problem, except that the environment settings are
coming from the shell environment and not a setttings.xml
Ellecer
On Mon, Nov 23, 2009 at 6:16 PM, Brett Randall javabr...@gmail.com wrote:
Hi Ellecer,
Is there a chance you are seeing http://jira.codehaus.org/browse/MNG-4148 ,
which is duplicated by http://jira.codehaus.org/browse/MNG-2626 ? Does that
fit your parent POM hierarchy?
Other Brett
On Mon, Nov 23, 2009 at 2:17 PM, Ellecer Valencia elle...@gmail.com wrote:
On Mon, Nov 23, 2009 at 11:18 AM, Brett Porter br...@apache.org wrote:
Did you also export WL_HOME?
I tried something similar here and it works fine in 2.2.1.
- Brett
Hi Brett,
I'd presume the environment variable being there means that's already
happened. =)
This entry is in .bashrc so I'm pretty sure the environment var is
always created.
export WL_HOME=/usr/java/weblogic
I've just created a new session window and see these errors when I run
with mvn -o -X -e package
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.
Ellecer
On 23/11/2009, at 10:08 AM, Ellecer Valencia wrote:
But that's exactly the problem - it *is* defined in the environment. :(
$ls -l $WL_HOME/server/lib/webservices.jar
-rwxr-xr-x. 1 dev dev 1696324 2009-10-30 16:55
/usr/java/weblogic/server/lib/webservices.jar
$echo $WL_HOME
/usr/java/weblogic
The Maven project I am trying to build has a pom.xml with a parent pom
parent
artifactIdsuper_pom/artifactId
groupIdmypackage/groupId
version1.0.2-SNAPSHOT/version
/parent
and it's in super_pom where the weblogic dependency is declared.
On Mon, Nov 23, 2009 at 9:18 AM, Brian Fox bri...@infinity.nu wrote:
Well Maven sees it just like the message:
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
So since the first one works and the second one doesn't, that leads me
to believe that WL_HOME isn't defined in your environment.
On Sun, Nov 22, 2009 at 9:06 AM, Ellecer Valencia elle...@gmail.com
wrote:
Hi Brian,
Could you please clarify what's actually plain wrong about it?
Going back to the example I posted:
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
Do you mean the first one, referencing ${java.home} is correct and
the one referencing ${env.WL_HOME} is wrong? So what should we do to
make it work?
thanks,
Ellecer
On Sat, Nov 21, 2009 at 4:33 AM, Brian E. Fox bri...@infinity.nu
wrote:
Maybe 2.2.2 will fix it. =)
Not likely. The pom is plain wrong an it was a bug in 2.x which
allowed it
to go unnoticed.
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall javabr...@gmail.com
wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log
that
:).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia
elle...@gmail.com
wrote:
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,
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
Hi Brian,
Could you please clarify what's actually plain wrong about it?
Going back to the example I posted:
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
Do you mean the first one, referencing ${java.home} is correct and
the one referencing ${env.WL_HOME} is wrong? So what should we do to
make it work?
thanks,
Ellecer
On Sat, Nov 21, 2009 at 4:33 AM, Brian E. Fox bri...@infinity.nu wrote:
Maybe 2.2.2 will fix it. =)
Not likely. The pom is plain wrong an it was a bug in 2.x which allowed it
to go unnoticed.
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall javabr...@gmail.com
wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that
:).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia elle...@gmail.com
wrote:
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
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdwebservices/artifactId
version10.0/version
scopesystem/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 javabr...@gmail.com
wrote:
Hi Ellecer
What is the output of mvn -e -X ...
Brett
On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia elle...@gmail.com
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
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
Well Maven sees it just like the message:
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
So since the first one works and the second one doesn't, that leads me
to believe that WL_HOME isn't defined in your environment.
On Sun, Nov 22, 2009 at 9:06 AM, Ellecer Valencia elle...@gmail.com wrote:
Hi Brian,
Could you please clarify what's actually plain wrong about it?
Going back to the example I posted:
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
Do you mean the first one, referencing ${java.home} is correct and
the one referencing ${env.WL_HOME} is wrong? So what should we do to
make it work?
thanks,
Ellecer
On Sat, Nov 21, 2009 at 4:33 AM, Brian E. Fox bri...@infinity.nu wrote:
Maybe 2.2.2 will fix it. =)
Not likely. The pom is plain wrong an it was a bug in 2.x which allowed it
to go unnoticed.
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall javabr...@gmail.com
wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that
:).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia elle...@gmail.com
wrote:
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
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdwebservices/artifactId
version10.0/version
scopesystem/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 javabr...@gmail.com
wrote:
Hi Ellecer
What is the output of mvn -e -X ...
Brett
On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia elle...@gmail.com
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
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
But that's exactly the problem - it *is* defined in the environment. :(
$ls -l $WL_HOME/server/lib/webservices.jar
-rwxr-xr-x. 1 dev dev 1696324 2009-10-30 16:55
/usr/java/weblogic/server/lib/webservices.jar
$echo $WL_HOME
/usr/java/weblogic
The Maven project I am trying to build has a pom.xml with a parent pom
parent
artifactIdsuper_pom/artifactId
groupIdmypackage/groupId
version1.0.2-SNAPSHOT/version
/parent
and it's in super_pom where the weblogic dependency is declared.
On Mon, Nov 23, 2009 at 9:18 AM, Brian Fox bri...@infinity.nu wrote:
Well Maven sees it just like the message:
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
So since the first one works and the second one doesn't, that leads me
to believe that WL_HOME isn't defined in your environment.
On Sun, Nov 22, 2009 at 9:06 AM, Ellecer Valencia elle...@gmail.com wrote:
Hi Brian,
Could you please clarify what's actually plain wrong about it?
Going back to the example I posted:
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
Do you mean the first one, referencing ${java.home} is correct and
the one referencing ${env.WL_HOME} is wrong? So what should we do to
make it work?
thanks,
Ellecer
On Sat, Nov 21, 2009 at 4:33 AM, Brian E. Fox bri...@infinity.nu wrote:
Maybe 2.2.2 will fix it. =)
Not likely. The pom is plain wrong an it was a bug in 2.x which allowed it
to go unnoticed.
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall javabr...@gmail.com
wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that
:).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia elle...@gmail.com
wrote:
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
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdwebservices/artifactId
version10.0/version
scopesystem/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
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
Did you also export WL_HOME?
I tried something similar here and it works fine in 2.2.1.
- Brett
On 23/11/2009, at 10:08 AM, Ellecer Valencia wrote:
But that's exactly the problem - it *is* defined in the environment. :(
$ls -l $WL_HOME/server/lib/webservices.jar
-rwxr-xr-x. 1 dev dev 1696324 2009-10-30 16:55
/usr/java/weblogic/server/lib/webservices.jar
$echo $WL_HOME
/usr/java/weblogic
The Maven project I am trying to build has a pom.xml with a parent pom
parent
artifactIdsuper_pom/artifactId
groupIdmypackage/groupId
version1.0.2-SNAPSHOT/version
/parent
and it's in super_pom where the weblogic dependency is declared.
On Mon, Nov 23, 2009 at 9:18 AM, Brian Fox bri...@infinity.nu wrote:
Well Maven sees it just like the message:
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
So since the first one works and the second one doesn't, that leads me
to believe that WL_HOME isn't defined in your environment.
On Sun, Nov 22, 2009 at 9:06 AM, Ellecer Valencia elle...@gmail.com wrote:
Hi Brian,
Could you please clarify what's actually plain wrong about it?
Going back to the example I posted:
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
Do you mean the first one, referencing ${java.home} is correct and
the one referencing ${env.WL_HOME} is wrong? So what should we do to
make it work?
thanks,
Ellecer
On Sat, Nov 21, 2009 at 4:33 AM, Brian E. Fox bri...@infinity.nu wrote:
Maybe 2.2.2 will fix it. =)
Not likely. The pom is plain wrong an it was a bug in 2.x which allowed it
to go unnoticed.
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall javabr...@gmail.com
wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that
:).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia elle...@gmail.com
wrote:
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
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdwebservices/artifactId
version10.0/version
scopesystem/scope
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
On Mon, Nov 23, 2009 at 11:18 AM, Brett Porter br...@apache.org wrote:
Did you also export WL_HOME?
I tried something similar here and it works fine in 2.2.1.
- Brett
Hi Brett,
I'd presume the environment variable being there means that's already
happened. =)
This entry is in .bashrc so I'm pretty sure the environment var is
always created.
export WL_HOME=/usr/java/weblogic
I've just created a new session window and see these errors when I run
with mvn -o -X -e package
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.
Ellecer
On 23/11/2009, at 10:08 AM, Ellecer Valencia wrote:
But that's exactly the problem - it *is* defined in the environment. :(
$ls -l $WL_HOME/server/lib/webservices.jar
-rwxr-xr-x. 1 dev dev 1696324 2009-10-30 16:55
/usr/java/weblogic/server/lib/webservices.jar
$echo $WL_HOME
/usr/java/weblogic
The Maven project I am trying to build has a pom.xml with a parent pom
parent
artifactIdsuper_pom/artifactId
groupIdmypackage/groupId
version1.0.2-SNAPSHOT/version
/parent
and it's in super_pom where the weblogic dependency is declared.
On Mon, Nov 23, 2009 at 9:18 AM, Brian Fox bri...@infinity.nu wrote:
Well Maven sees it just like the message:
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
So since the first one works and the second one doesn't, that leads me
to believe that WL_HOME isn't defined in your environment.
On Sun, Nov 22, 2009 at 9:06 AM, Ellecer Valencia elle...@gmail.com wrote:
Hi Brian,
Could you please clarify what's actually plain wrong about it?
Going back to the example I posted:
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
Do you mean the first one, referencing ${java.home} is correct and
the one referencing ${env.WL_HOME} is wrong? So what should we do to
make it work?
thanks,
Ellecer
On Sat, Nov 21, 2009 at 4:33 AM, Brian E. Fox bri...@infinity.nu wrote:
Maybe 2.2.2 will fix it. =)
Not likely. The pom is plain wrong an it was a bug in 2.x which allowed it
to go unnoticed.
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall javabr...@gmail.com
wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that
:).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia elle...@gmail.com
wrote:
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
groupIdcom.sun/groupId
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
Hi Ellecer,
Is there a chance you are seeing http://jira.codehaus.org/browse/MNG-4148 ,
which is duplicated by http://jira.codehaus.org/browse/MNG-2626 ? Does that
fit your parent POM hierarchy?
Other Brett
On Mon, Nov 23, 2009 at 2:17 PM, Ellecer Valencia elle...@gmail.com wrote:
On Mon, Nov 23, 2009 at 11:18 AM, Brett Porter br...@apache.org wrote:
Did you also export WL_HOME?
I tried something similar here and it works fine in 2.2.1.
- Brett
Hi Brett,
I'd presume the environment variable being there means that's already
happened. =)
This entry is in .bashrc so I'm pretty sure the environment var is
always created.
export WL_HOME=/usr/java/weblogic
I've just created a new session window and see these errors when I run
with mvn -o -X -e package
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.
Ellecer
On 23/11/2009, at 10:08 AM, Ellecer Valencia wrote:
But that's exactly the problem - it *is* defined in the environment. :(
$ls -l $WL_HOME/server/lib/webservices.jar
-rwxr-xr-x. 1 dev dev 1696324 2009-10-30 16:55
/usr/java/weblogic/server/lib/webservices.jar
$echo $WL_HOME
/usr/java/weblogic
The Maven project I am trying to build has a pom.xml with a parent pom
parent
artifactIdsuper_pom/artifactId
groupIdmypackage/groupId
version1.0.2-SNAPSHOT/version
/parent
and it's in super_pom where the weblogic dependency is declared.
On Mon, Nov 23, 2009 at 9:18 AM, Brian Fox bri...@infinity.nu wrote:
Well Maven sees it just like the message:
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
So since the first one works and the second one doesn't, that leads me
to believe that WL_HOME isn't defined in your environment.
On Sun, Nov 22, 2009 at 9:06 AM, Ellecer Valencia elle...@gmail.com
wrote:
Hi Brian,
Could you please clarify what's actually plain wrong about it?
Going back to the example I posted:
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
Do you mean the first one, referencing ${java.home} is correct and
the one referencing ${env.WL_HOME} is wrong? So what should we do to
make it work?
thanks,
Ellecer
On Sat, Nov 21, 2009 at 4:33 AM, Brian E. Fox bri...@infinity.nu
wrote:
Maybe 2.2.2 will fix it. =)
Not likely. The pom is plain wrong an it was a bug in 2.x which
allowed it
to go unnoticed.
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall javabr...@gmail.com
wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log
that
:).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia
elle...@gmail.com
wrote:
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
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
Maybe 2.2.2 will fix it. =)
Not likely. The pom is plain wrong an it was a bug in 2.x which
allowed it to go unnoticed.
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall javabr...@gmail.com
wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log
that :).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia
elle...@gmail.com wrote:
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
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/
systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdwebservices/artifactId
version10.0/version
scopesystem/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 javabr...@gmail.com
wrote:
Hi Ellecer
What is the output of mvn -e -X ...
Brett
On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia elle...@gmail.com
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---
--
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
[WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
Hi Ellecer What is the output of mvn -e -X ... Brett On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia elle...@gmail.comwrote: 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
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
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdwebservices/artifactId
version10.0/version
scopesystem/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 javabr...@gmail.com wrote:
Hi Ellecer
What is the output of mvn -e -X ...
Brett
On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia elle...@gmail.comwrote:
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that :).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia elle...@gmail.com wrote:
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
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdwebservices/artifactId
version10.0/version
scopesystem/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 javabr...@gmail.com
wrote:
Hi Ellecer
What is the output of mvn -e -X ...
Brett
On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia elle...@gmail.com
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
No, not my team. I think a more sensible fix is to just put the
weblogic jars in Artifactory, but it's in a pom that I don't have much
control over.
Maybe 2.2.2 will fix it. =)
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall javabr...@gmail.com wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that :).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia elle...@gmail.com wrote:
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
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/../lib/tools.jar/systemPath
/dependency
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdwebservices/artifactId
version10.0/version
scopesystem/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 javabr...@gmail.com
wrote:
Hi Ellecer
What is the output of mvn -e -X ...
Brett
On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia elle...@gmail.com
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
