I was having the same error the other day, the way I fixed it was by changing
the groupId for opensymphony in the /core/pom.xml, there are only two places
that it appears in the plugins and the dependencies:
from:
<groupId>com.opensymphony.xwork</groupId>
to
<groupId>opensymphony</groupId>
this should work :-) I do not know the technical details as to why it is not
working as it is at the moment though. My guess is that the opensymphony guys
changed the mvn repository directory name.
HTH
-Cesar
----- Original Message ----
From: Nils-Helge Garli <[EMAIL PROTECTED]>
To: Struts Developers List <dev@struts.apache.org>
Sent: Tuesday, September 11, 2007 10:52:32 AM
Subject: Re: xwork groupId change
I keep getting build failures saying maven can't find xwork 2.1-SNAPSHOT:
------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: com.opensymphony.xwork
ArtifactId: xwork
Version: 2.1-SNAPSHOT
Reason: 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=com.opensymphony.xwork -DartifactId=xwork
\
-Dversion=2.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
com.opensymphony.xwork:xwork:jar:2.1-SNAPSHOT
from the specified remote repositories:
Maven Snapshots (http://snapshots.maven.codehaus.org/maven2/),
central (http://repo1.maven.org/maven2),
opensymphony (http://maven.opensymphony.com),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
snapshots-maven-codehaus (http://snapshots.maven.codehaus.org/maven2)
-----------
Is this in some way related to this? And how do I fix it? Is there a
snapshot repository I'm missing in my local settings.xml file?
Nils-H
On 9/2/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On 9/2/07, Konstantin Priblouda <[EMAIL PROTECTED]> wrote:
>
> > diffucult to tell. but recently ( friday )
> > I got velocity included in war twice with different
> > versions and that produced lot of weird errors
> > on classloading and resolving methods *sometimes*
> > (on different boxes)
> >
> > it turned out, that velocity is sometimes referred by
> > group Id as org.apache.velocity or just velocity -
> > when
> > changing groups be carefull and check who uses it...
>
> This happens when a project changes groupIds without "relocating" the
> old versions in the repository. Maven has no way of knowing that
> 'velocity' and 'org.apache.velocity' are the same thing.
>
> There's a guide here:
> http://maven.apache.org/guides/mini/guide-relocation.html
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
