Yes, I agree with Martin. Perhaps a better way would be to patch the release plugin so that it accepts SNAPSHOTs. Since I have dived into maven this week for a rather complex project at my company, I'm no longer a total maven newby. Hope I can afford some time next week to bring in my new knowledge into MyFaces. As as starter I can have a look at the release plugin sourcecode and see what's possible - but not before monday.
WDYT? Manfred On 2/11/06, Martin Marinschek <[EMAIL PROTECTED]> wrote: > I don't even see why you need to be forced to use the final version of > a plugin - you can have an alpha-state plugin doing something on a > very mature project. > > regards, > > Martin > > On 2/11/06, Sean Schofield <[EMAIL PROTECTED]> wrote: > > I also posted about issue on the maven dev list. There is definitely > > room for improvement in the release plugin. It doesn't really > > envision you creating a branch for a release that will be down the > > road some time. I don't see why we need to switch to final versions > > of a plugin until we are actually ready to release. Of course we > > could skip the plugin but maven automates some of the important tasks > > for you. > > > > Sean > > > > On 2/11/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > > > The biggest issue is the XSLT plugin. That is a snapshot and its not > > > > a myfaces plugin. The only solution I can think of is to add it to > > > > the maven project as our own plugin and release it (with a myfaces > > > > group id.) Then when they finally get around to releasing the plugin > > > > we could switch to the official one. > > > > > > I am not that maven guy, but this kind of *work around* sounds ok for me. > > > > > > -Matthias > > > > > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces >
