2009/9/7 is_maximum <[email protected]> > > > > Dan Tran wrote: > > > > Release plugin cannot proceed with snapshot dependencies including > > build plugin. > > The main rational is it want to guarantee the release code is > > producible. Note snapshots > > can go away any time and it can have behaviors changed any time. > > > > -D > > > > > > Yes that's right but this guarantee could be optional. > I think the person in charge while releasing know his job and this is not > going to blow everything up so This is him/her that decide whether the > release contains SNAPSHOT or not > > I still think that checking maven plugins versions doesn't make sense > because once we make a release version you can see no jar file from any > maven plugin uin your release unless your project is a maven plugin project > > for example, in our project we have a plugin for jaxb and it is a snapshot > version, I use this to create a xsd file each time I compile my project, > why > do I need to comment this plugin during a release process because the > release plugin don't like that. > > I do not mean to appear rude...
If you don't like the way the release plugin works, you can always write your own. The considered opinion of most people is that the current checks in the release plugin are entirely necessary, and the minimal set of checks in order to ensure that any release can be completely and reliably reproduced at a later point in time. If you feel differently, the core module used the the release plugin is available as a dependency, so you would not have much writing to do -Stephen > Thanks > > > ----- > -- > Regards > Mohammad > http://pixelshot.wordpress.com Pixelshot > -- > View this message in context: > http://n2.nabble.com/problem-regarding-maven-release-plugin-tp3595500p3599014.html > Sent from the maven users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
