On 3/11/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
I believe Don said Plug-ins could be used in other projects... theoretically even Struts 1. So it's technically a separate project with its own build cycle.
Unless and until an actual community forms around Struts Annotations and other people start to use it, there's no value added by giving the bits their own build cycle. People can do all the same things with it, regardless. Meanwhile, there's is value lost by complicating the Struts 2 release. If an independent community does collect around annotation, then it would be worth making it a separate release, because there would be more people to help.
As for the Archetype (and anything else), if it is exclusive to Struts 2, then I believe those should go with the Struts 2 build. The POM? Which POM? Struts 1 and Struts 2 both have a parent POM, but those also have a parent POM shared across both. Right? The grandparent needs its own release, but the immediate parent does not, imo.
Even so, the Struts 2 POM is already a separate release. Since Struts 2 does not have any subprojects, why not release the S2 POM with everything else?
Paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
