On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
Annotations was originally setup as a separate JAR with an independent version so as to encourage reuse. However, until other product indicate an interest in using Annotaitons and participating in its development, managing a separate release process provides no tangible benefit.
It provides the tangible benefit of actually allowing for reuse... Therefore, it's proposed that annotations become a part of
the general Struts 2 distribution, along with the various plugins, but remain in its own JAR, so as to encourage reuse. If an independent community forms around Annotations, we can revisit the issue of making it a subproject with its own release cycle.
An independent community is simply not going to form around something that's buried inside of Struts. We've already seen that in the past. I know this is a bit of a Catch 22 situation, but unless we actually allow for reuse in the first place, as we do today, there is very little chance that it will ever be reused. Therefore I would prefer to see the annotations stay separate. -- Martin Cooper Archetype was original setup as a separate entity, but it might be
simpler to reduce the number of independent artifacts being released by the project. The S2 Release Manager will have to update the version number in the templates, but that seems like less work that coordinating tandem releases, that might end up being handled by the same volunteer anyway. Again, this is as to the trunk. For now, we can let the 2.0 branch stay as it is. Further thoughts? -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
