Error: Could not resolve dependencies for project from local repository because of _maven.repositories
Hi, My situation is not really unusual. I have a workaround for it, but I'm trying to see if there are any other options, ones that fit with Maven but don't require me to install a repository manager on my home PC. :) I zipped up a copy of a project from work, and my maven repository, and set it up on my home computer. However, I'm getting these messages about Maven not being able to find the dependencies. Non-resolvable parent POM: The repository system is offline but the artifact [corporate pom details] is not available in the local repository. and 'parent.relativePath' points at wrong local POM At first I just manually installed the corporate POM, but then it led to more errors about other dependencies not being found. Dependencies that were present in my repository. Now I know it's related to the repository indicated in _maven.repositories file (it's referring to the ID of my work repo). The quick fix is to just do cd ~/.m2 find . -name '_maven.repositories' -type f -delete Is there any other recommended way to deal with this situation? Using the -o parameter for offline didn't work, even using Maven 3.0.4. Is there somewhere that I could tell Maven to just treat the local repository as the corporate repo named in _maven.repositories? This is covering some issues last discussed here, in Maven 3, _maven.repositories and *lastUpdated http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html And a related issue: http://jira.codehaus.org/browse/MNG-5185 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 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, type=jar
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
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
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
artifactIdtools
[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 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
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
Getting error The defined artifact is not an archetype with AppFuse archetypes
Hi, I'm trying to use mvn archetype:generate to create some projects and noticed that the AppFuse archetypes are generating errors like: Downloading: http://repo1.maven.org/maven2/org/appfuse/archetypes/appfuse-core/2.1.0-M1/appfuse-core-2.1.0-M1.jar [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The defined artifact is not an archetype [INFO] Is anyone else getting these errors? I've tested it with archetypes 1-9 (all the AppFuse ones) and they're returning the same error I'm using maven 2.0.10 - have these archetypes changed to now require higher versions, or does anyone else know what's happening with them? thanks, Ellecer - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting error The defined artifact is not an archetype with AppFuse archetypes
Matt has emailed back about this. Would be best to do it from command-line, using the page he mentions to create the entire command. -- Forwarded message -- From: Matt Raible Date: Thu, Nov 19, 2009 at 2:44 PM Subject: Re: CP: Problem with Appfuse Maven Archetypes In 2.1.0-M1, we've changed the name of the archetypes. If you append -archetype onto the name, it should work. The following page might make it easier (this is also shown in the QuickStart Guide). http://static.appfuse.org/archetypes.html FWIW, I just released 2.1.0-M1 today and plan on writing up a blog post, release notes, etc. tomorrow. Matt On Thu, Nov 19, 2009 at 2:02 PM, Wayne Fay wayne...@gmail.com wrote: Is anyone else getting these errors? I've tested it with archetypes 1-9 (all the AppFuse ones) and they're returning the same error You should probably ask Matt Raible what's going on with these archetypes... I'm using maven 2.0.10 - have these archetypes changed to now require higher versions, or does anyone else know what's happening with them? Did you try with Maven 2.2.1? Wayne - 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
maven-install-plugin-2.3 is missing from main Maven repository at repo1.maven.org
Hi, We've just had a problem with a build that was looking for the latest maven-install-plugin, which is 2.3. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-install-plugin -Dversion=2.3 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-install-plugin -Dversion=2.3 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3 I've looked at http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3/ and the jar file isn't there. The sources and javadoc jar files are present. Are these files being uploaded manually or automatically? Was it just mistakenly deleted? Thanks for your help, Ellecer - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-install-plugin-2.3 is missing from main Maven repository at repo1.maven.org
Great, thanks guys! I'll try to move all of our stuff to start using maven 2.0.9 or higher. On Thu, Mar 26, 2009 at 1:18 PM, Brian E. Fox bri...@reply.infinity.nu wrote: The jar is now on central and is being pushed again to all 1st level mirrors. -Original Message- From: Brett Porter [mailto:br...@apache.org] Sent: Wednesday, March 25, 2009 9:48 PM To: Maven Users List Subject: Re: maven-install-plugin-2.3 is missing from main Maven repository at repo1.maven.org We're trying to recover the release artifact that seems to have been lost in transit. To work around this, you should add maven-install-plugin to your POM with the previous version (2.2). This is a good practice for reproducibility regardless, and in place by default in Maven 2.0.9+. Cheers, Brett On 26/03/2009, at 11:01 AM, Ellecer Valencia wrote: Hi, We've just had a problem with a build that was looking for the latest maven-install-plugin, which is 2.3. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-install-plugin -Dversion=2.3 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-install-plugin -Dversion=2.3 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3 I've looked at http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plu gin/2.3/ and the jar file isn't there. The sources and javadoc jar files are present. Are these files being uploaded manually or automatically? Was it just mistakenly deleted? Thanks for your help, Ellecer - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - 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
Maven descriptor - what is it good for?
I'm trying to clarify what is the purpose of the Maven descriptor, and
what systems make use of it, and if there is any point in working on
this issue we have with the pom.xml that is added to our generated
artifacts.
Our projects are set up to have their version numbers passed in via
the build system. When a build is performed on Hudson, it passes in
the property major.minor.version and BUILD_NUMBER.
So the version element in our pom.xml looks like this:
version${major.minor.version}.${BUILD_NUMBER}/version
and the build command in the Hudson config for this project is like this
mvn -Dmajor.minor.version=1.0.0 -DBUILD_NUMBER=${BUILD_NUMBER} clean package
(actually, Hudson sets BUILD_NUMBER in the environment so we can also
leave it out)
Now the problem is, when the pom.xml gets added to the generated
artifact, it's the same as the original pom.xml, so that the version
is still
version${major.minor.version}.${BUILD_NUMBER}/version
and does not get the details passed in on the command line. Is this a
bug or how it's really supposed to work?
I would've thought it would pick up on the parameters that have been
set and add a pom.xml that is more like the one you get when you do
mvn help:effective-pom
The pom.properties has all the right values, so the version property
has whatever values were passed in from command line.
It's not a major issue, but it's a small annoyance when you upload it
manually via Artifactory and it thinks that the version of the
artifact is the string ${major.minor.version}.${BUILD_NUMBER}.
It would be great if other users or maven developers could clarify
what it is used for, and if the behaviour I'm seeing is intentional.
(btw, am using Maven 2.0.8)
thanks,
Ellecer
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
