-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In working on the Mavenization of Tapestry, I have a fundamental
question. Which portions of Tapestry are we wanting to have their own
release cycle and which portions do we want separate for development,
but released as a part of Tapestry itself?
Current 5.x development looks like the following:
tapestry5/
tapestry-core/
branches/
tags/
trunk/
- --which would imply the following:
tapestry-contrib/
branches/
tags/
trunk/
tapestry-annotations/
branches/
tags/
trunk/
- --etc. This would give each "tapestry-*" its own release cycle, but
would create something of a headache when saying "We use Tapestry
version X".
My thoughts run along these lines:
tapestry/
contrib/
branches/
tags/
trunk/
branches/
tags/
trunk/
annotations/
api/
core/
library/
This allows 'tapestry' to be 'trunk' - saying "We use Tapestry version X
and Tapestry-Contrib version Y". (I see the "Tapestry Framework" being
more than just "core" - and would really like the internal separation to
go into 'api') Note that I also broke away from the 'default maven' idea
of "tapestry-contrib-X.x.jar" comes from "tapestry-contrib" - it would
come from "tapestry/contrib" allowing us to check out "tapestry/trunk"
and get all that we need for "tapestry-X.x.jar" and
"tapestry/contrib/trunk" to get all we need for "tapestry-contrib-X.x.jar".
Bottom line question is as above: What is a "sub-project" and what is a
"module" in the main project. That kind of decides the structure and I
can get Maven to adapt where it's not "the default".
Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEU7cQaCoPKRow/gARAsiQAKCYRP2VBjpqefHyajmiUU8vq0DaMwCdFlhM
2+jvReg2UKqx/ANOtLfixcE=
=ywr+
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
