It doesn't help your argument to use Maven as an example :) I think it is pretty straight forward - all plugins have versions, only the bundled plugins are versioned/released along with the rest of Struts to make it simpler. If we gave each plugin its own version, which we did with Struts 1, it gets really confusing really quickly what versions are meant to go with what releases. For the occasional third-party plugin with its own release cycle, this is a necessary evil, but for the core plugins, it is a huge source of confusion to users.
Don On 2/23/08, Antonio Petrelli <[EMAIL PROTECTED]> wrote: > 2008/2/23, Al Sutton <[EMAIL PROTECTED]>: > > > So what happens if a plug-in is added to the core (e.g. a YUI and/or GWT > > plugin to compliment the dojo one), does that necessitate a 2.2? > > > This is The Good Question :-) > As I wrote a lot of time before, IMHO every plugin should be treated > as a different project, with its own version number, a-la Maven. > This suggestion has not been taken into consideration and we are > suffering the consequences, because lots of Struts 2 plugins are > coming out day by day. > > Antonio > > > --------------------------------------------------------------------- > 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]
