On 3/11/07, Martin Cooper <[EMAIL PROTECTED]> wrote:
Unless I'm missing something, it's because we want to be able to release
some pieces (e.g. plugins) without requiring a corresponding release of
'core'. If a plugin depends on an updated version of struts-annotations (or
whatever), it shouldn't have to wait for a 'core' release to get a new
released version of it.
Naaahhh... we're talking about whether to bring struts-annotations and
the archetypes into struts2/trunk (or the branch, I'm not entirely
sure).
I say go for it... my objection to bringing the archetypes in is not
technical, it's that the release manager will be required to manually
change the version numbers in the templates. Since the active release
manager is pushing for the change, that's not an issue. :)
Struts Annotations bothers me a little... you'll have to use
${version} in the struts2-core pom but again this is a build-time
thing, it won't break any users.
(I think we should leave struts-master out of it-- we've already got
the list of committers in three places that rarely match up--
STATUS.txt, pom.xml, volunteers.xml.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
