Hi Well, in myfaces there are projects that use plugins hosted in myfaces. For example, myfaces-builder-plugin is required to build myfaces-core. In some moments, it appear bugs on core that require some changes on myfaces-builder-plugin, so in those moments we need a plugin snapshot, just while we release the plugin.
If maven release plugin check for snapshot plugins usage before release (and do not allow if that's the case), why bother us to change the pom every time a bug like this happens? regards, Leonardo Uribe 2010/11/5 David Jencks <[email protected]> > I think a plugin snapshot repo is not in the asf master pom because using > snapshot plugins is not something the maven devs want to encourage. Why > does myfaces need a snapshot plugin? I'd recommend putting the plugin repo > entry near the use of the plugin so it can be removed easily when the plugin > is released. I'd include a comment on why its needed too. > > thanks > david jencks > > On Nov 5, 2010, at 1:49 AM, Matthias Wessendorf wrote: > > > Hi, > > > > the ASF master-pom does contain a _regular_ snapshot repo (linked to > > the (new) nexus repo), see: > > https://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml > > > > *snip* > > <repository> > > <id>apache.snapshots</id> > > <name>Apache Snapshot Repository</name> > > <url>http://repository.apache.org/snapshots</url> > > <releases> > > <enabled>false</enabled> > > </releases> > > </repository> > > *snip* > > > > > > However, it doesn't define the "apache.snapshot" for plugins. Nor does > > the myfaces pom. > > Does one know why? > > > > In Trinidad we currently have this setting: > > <pluginRepositories> > > <pluginRepository> > > <id>apache.snapshots</id> > > <name>Apache Snapshot Repository</name> > > <url>http://repository.apache.org/snapshots</url> > > <releases> > > <enabled>false</enabled> > > </releases> > > </pluginRepository> > > </pluginRepositories> > > > > IMO it could be centralized: In myfaces-pom or in the ASF pom. > > > > Thoughts? > > > > -Matthias > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > >
