You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Siegmann Daniel, NY" <Da...@fja-us.com> on 2007/06/07 16:58:41 UTC
[M2] Avoiding snapshot plugins
I get the following error trying to build the Maven site:
Failed to resolve artifact, possibly due to a repository list that is
not appropriately equipped for this artifact's metadata.
org.apache.maven.skins:maven-default-skin:jar:1.1-SNAPSHOT
The POM file of this project is not configured to use any specific
versions of plugins. I don't really care what version is chosen, but I
do not want it to use snapshot versions, especially those which are not
in the central repository!
Anyone know why Maven is trying to find this snapshot, and how I can
stop Maven from doing so?
--
Daniel Siegmann
FJA-US, Inc.
512 Seventh Ave., New York, NY 10018
(212) 840-2618 ext. 139
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [M2] Avoiding snapshot plugins (fixed)
Posted by "Siegmann Daniel, NY" <Da...@fja-us.com>.
Skins aren't dependencies or plugins, at least they're not used as such
here. It seems it is selected programmatically (I went looking through
the source code).
However, I figured out the problem. The metadata in our Maven proxy
listed just the snapshot version. When I deleted out what was in our
proxy and let it re-download, the release version (1.0) was correctly
found.
Anyway, thanks for the help.
--
Daniel Siegmann
FJA-US, Inc.
512 Seventh Ave., New York, NY 10018
(212) 840-2618 ext. 139
-----Original Message-----
From: Wayne Fay [mailto:waynefay@gmail.com]
Sent: Thursday, June 07, 2007 11:03 AM
To: Maven Users List
Subject: Re: [M2] Avoiding snapshot plugins
Search / grep the pom files in your .m2 repo for "maven-default-skin"
and see if one of them has brought in this SNAPSHOT dependency. If
you've got a released plugin downloaded from Central and it has this
SNAPSHOT dependency, that is clearly a bug and the Maven Dev team will
want to address it.
Also, try mvn -X to see the dependency stack which should show where
this SNAPSHOT is being brought in.
Finally, its a good idea to specify versions of all dependencies and
plugins, to avoid surprises like this.
Wayne
On 6/7/07, Siegmann Daniel, NY <Da...@fja-us.com> wrote:
> I get the following error trying to build the Maven site:
>
> Failed to resolve artifact, possibly due to a repository list that is
> not appropriately equipped for this artifact's metadata.
> org.apache.maven.skins:maven-default-skin:jar:1.1-SNAPSHOT
>
> The POM file of this project is not configured to use any specific
> versions of plugins. I don't really care what version is chosen, but I
> do not want it to use snapshot versions, especially those which are
> not in the central repository!
>
> Anyone know why Maven is trying to find this snapshot, and how I can
> stop Maven from doing so?
>
> --
> Daniel Siegmann
> FJA-US, Inc.
> 512 Seventh Ave., New York, NY 10018
> (212) 840-2618 ext. 139
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [M2] Avoiding snapshot plugins
Posted by Wayne Fay <wa...@gmail.com>.
Search / grep the pom files in your .m2 repo for "maven-default-skin"
and see if one of them has brought in this SNAPSHOT dependency. If
you've got a released plugin downloaded from Central and it has this
SNAPSHOT dependency, that is clearly a bug and the Maven Dev team will
want to address it.
Also, try mvn -X to see the dependency stack which should show where
this SNAPSHOT is being brought in.
Finally, its a good idea to specify versions of all dependencies and
plugins, to avoid surprises like this.
Wayne
On 6/7/07, Siegmann Daniel, NY <Da...@fja-us.com> wrote:
> I get the following error trying to build the Maven site:
>
> Failed to resolve artifact, possibly due to a repository list that is
> not appropriately equipped for this artifact's metadata.
> org.apache.maven.skins:maven-default-skin:jar:1.1-SNAPSHOT
>
> The POM file of this project is not configured to use any specific
> versions of plugins. I don't really care what version is chosen, but I
> do not want it to use snapshot versions, especially those which are not
> in the central repository!
>
> Anyone know why Maven is trying to find this snapshot, and how I can
> stop Maven from doing so?
>
> --
> Daniel Siegmann
> FJA-US, Inc.
> 512 Seventh Ave., New York, NY 10018
> (212) 840-2618 ext. 139
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org