Thanks for pointing this out. So, it is a bug in Nexus.
I will upgrade to 1.8.0.
On 11/11/10 2:54 AM, Nord, James wrote:
Or upgrade to 1.8.0
https://issues.sonatype.org/browse/NEXUS-3729
/James
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Anders Hammar
Sent: 11 November 2010 09:07
To: Maven Users List
Subject: Re: maven-metadata containing SNAPSHOT versions when Nexus group
references release proxy repo
I think the problem is that you're proxying one of the repo groups of
JBoss's Nexus instance. That one includes the apache snapshots, which is
intentional:
http://community.jboss.org/message/564903#564903
Instead, proxy the appropriate release repos. The jboss repo group 'public'
also proxies Maven central I believe, which you don't want.
There's info about the new nexus instance at JBoss at the JBoss blog:
http://community.jboss.org/en/build/blog
You should be able to find info there regarding which repos you should
proxy.
/Anders
On Thu, Nov 11, 2010 at 00:00, Jane Young<[email protected]> wrote:
I'm not sure if this is the right forum to post this question. If not,
please advice me where to post this question.
I setup a Nexus group repository that references several proxy
repositories. This group repo only references the released (non-SNAPSHOT)
artifacts.
The group repo references: JBoss Maven repo and Maven central repo.
The JBoss Maven repo contains SNAPSHOT artifacts (e.g.
https://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-enforcer-plugin/
)
and Maven central repo contains released versions (e.g.
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-enforcer-plugin/
)
The group repo should only contain the released version from Maven central:
See:
http://maven.glassfish.org/content/groups/glassfish/org/apache/maven/plugins/maven-enforcer-plugin/
However, the maven-metadata.xml file contains both SNAPSHOT and
non-SNAPSHOT:
http://maven.glassfish.org/content/groups/glassfish/org/apache/maven/plugins/maven-enforcer-plugin/maven-metadata.xml
This is creating some problem in our build since some of pom file do not
include the version of the plugin, so maven will try to download the latest
version, which is a SNAPSHOT version but the group repo does not have the
SNAPSHOT artifact.
Is this a bug? I have tried rebuilding metadata but it still contains
SNAPSHOT versions.
Is there a workaround?
Thanks,
Jane
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
**************************************************************************************
This message is confidential and intended only for the addressee. If you have
received this message in error, please immediately notify the
[email protected] and delete it from your system as well as any copies. The
content of e-mails as well as traffic data may be monitored by NDS for
employment and security purposes. To protect the environment please do not
print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX,
United Kingdom. A company registered in England and Wales. Registered no.
3080780. VAT no. GB 603 8808 40-00
**************************************************************************************
---------------------------------------------------------------------
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]
