Hi Raphaël, I assume you mean try it with a configuration like this:
<profile> <id>snapshot-plugins</id> <activation> <activeByDefault>true</activeByDefault> </activation> <repositories> <repository> <id>apache-snapshot-plugins</id> <name>apache-snapshot-plugins</name> <url>http://people.apache.org/repo/m2-snapshot-repository</url> <snapshots> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </snapshots> <releases> <enabled>false</enabled> </releases> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>apache-snapshot-plugins</id> <name>apache-snapshot-plugins</name> <url>http://people.apache.org/repo/m2-snapshot-repository</url> <snapshots> <enabled>true</enabled> <updatePolicy>always</updatePolicy> </snapshots> <releases> <enabled>false</enabled> </releases> </pluginRepository> </pluginRepositories> </profile> That also does not help. As you mentioned, I guess your repository manager masks this issue. This is not a critical issue for me at the moment though, so I guess we can just leave it to MNG-2974 for resolution. I can just install the latest plugin version locally where needed. Thanks, Brad -----Original Message----- From: Raphaël Piéroni <[EMAIL PROTECTED]> Reply-To: Maven Developers List <dev@maven.apache.org> To: Maven Developers List <dev@maven.apache.org> Subject: Re: [archetype] time to prepare a release of 2.0-alpha-4 Date: Wed, 17 Sep 2008 18:43:00 +0200 Hi Brad, Now you mention it, i can remember once having this problem. I removed my local version of the plugin and its libraries, even any archetype, i had. I didn't reproduced this. But i must admit having a nexus on my laptop that goes to the snapshot repository. Can you try with both a plugin repository and a regular repository in your settings. Regards, Raphaël 2008/9/17, Brad Szabo <[EMAIL PROTECTED]>: > Is anyone able to resolve the 2.0-alpha-4-SNAPSHOT version from the > command-line without a copy in his/her local repository? I cannot. It > would appear that this is a bug documented in > http://jira.codehaus.org/browse/MNG-2974, but I was just wondering if > perhaps someone is able to and I just have a problem with my SNAPSHOT > repository configuration in my settings.xml (I don't think so though): > > <profile> > <id>snapshot-plugins</id> > <activation> > <activeByDefault>true</activeByDefault> > </activation> > <pluginRepositories> > <pluginRepository> > <id>apache-snapshot-plugins</id> > <name>apache-snapshot-plugins</name> > <url>http://people.apache.org/repo/m2-snapshot-repository</url> > <snapshots> > <enabled>true</enabled> > <updatePolicy>always</updatePolicy> > </snapshots> > <releases> > <enabled>false</enabled> > </releases> > </pluginRepository> > </pluginRepositories> > </profile> > > Or is this just a well known bug that everyone works around by > installing SNAPSHOTs locally? > > Especially due to this issue, I am all for a release of 2.0-alpha-4! > > > Thanks, > Brad > > -----Original Message----- > From: Raphaël Piéroni <[EMAIL PROTECTED]> > Reply-To: Maven Developers List <dev@maven.apache.org> > To: Maven Developers List <dev@maven.apache.org> > Subject: Re: [archetype] time to prepare a release of 2.0-alpha-4 > > Date: Wed, 17 Sep 2008 08:26:05 +0200 > > > Hi Brad, > > I committed your patch yesterday. It is in the snapshot i uploaded yesterday. > > Yep, i was not planing to document it. But i know where to; > it is in the "handcrafting an archetype" example. > > Regards, > > Raphaël > > > 2008/9/17 Brad Szabo <[EMAIL PROTECTED]>: > > Hi Raphaël, > > > > The additional examples are helpful, thanks! > > > > Were you planning on mentioning the file renaming support > > (http://jira.codehaus.org/browse/ARCHETYPE-191) in these documentation > > updates, I don't see them. > > > > Do you think I should create a new JIRA for the enhanced file renaming > > support and move over the patches I posted to ARCHETYPE-191, since it > > is closed and those patches won't be incorporated for this release? > > > > Thanks, > > Brad > > > > > > -----Original Message----- > > From: Raphaël Piéroni <[EMAIL PROTECTED]> > > Reply-To: Maven Developers List <dev@maven.apache.org> > > To: Maven Developers List <dev@maven.apache.org> > > Subject: Re: [archetype] time to prepare a release of 2.0-alpha-4 > > Date: Tue, 16 Sep 2008 20:57:24 +0200 > > > > Hi folks, > > > > I think i documented enough for this release. > > > > Please review the documentation at > > http://people.apache.org/~rafale/site/maven-archetype-plugin/index.html > > > > I will be happy if any one can review the sources with respect to the > > apache licensing convention. > > > > I do not plan to enhance the plugin nor its documentation more. only > > to fix the typoes... > > > > I assume that if no objection is made during the review untill next > > friday (GMT+2), i will call the vote. the latest version of the plugin > > can be used with the snapshot deployed or building form sources. > > > > Regards > > > > Raphaël > > > > 2008/9/16, Raphaël Piéroni <[EMAIL PROTECTED]>: > >> 2008/9/13, Wendy Smoak <[EMAIL PROTECTED]>: > >> > >> > On Sat, Sep 13, 2008 at 7:13 AM, Raphaël Piéroni > >> > <[EMAIL PROTECTED]> wrote: > >> > > >> > >> Do you mean this gets created at build time? At run time? I know > I > >> > >> found a file in there to edit... > >> > > > >> > > what i do usually, is run the profile, > >> > > grab the catalog that was tested (printed on screen) then paste to > the catalog. > >> > > >> > > >> > Okay, thanks. The catalog we ship with a release of the plugin should > >> > not list any snapshots of archetypes. Can you change the code so that > >> > it excludes any snapshots it finds on the wiki page or will it be a > >> > manual review process? > >> > >> > >> Done, snapshot excluded from catalog creation. > >> > >> > > >> > > >> > -- > >> > >> > > >> > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]