On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
On 3/11/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote: > > > It's still not clear to me why it needs to be released separately. The > > justification for the archetypes almost makes sense, but creating a > > separate distribution for Struts Annotations still seems like busy > > work. > > No one objects to releasing the struts-master pom, and it's the same > situation. Struts 2 depends on struts-master, struts-annotations, and > a bunch of other things. We need released versions of all those things > because we are not supposed to release with snapshot dependencies. > > Unfortunately, until we start using Maven to do releases, I don't know what that means. What else would we need to do?
I believe Wendy is talking about 'mvn release', which theoretically takes care of a bunch of stuff all in one go.
checking for > those snapshots is a manual process. I see that 2.0.6 went out with > snapshot dependencies on both struts-annotations and > maven-dependency-plugin. Luckily, those are build-time dependencies, > so they won't affect anyone just *using* Struts 2. Why can't they all be released together?
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. -- Martin Cooper -Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
