Another way of looking at it is that such a tag would be capturing the
same information as the Maven POM... The main value of a tag is to allow
someone to check out all the code for a given release at once. Checking
out just action and letting Maven pull the release jars for the other
sub-projects gets you there anyway IMHO.
L.
Ted Husted wrote:
Did we tag current for the Struts-Shale_1.0.0 and
Struts-Scripting_1.0.0 releases?
For the Action Library, right now, I'm only planning to post the JARs
(including external dependencies), which are all self-tagged for the
appropriate release.
Conceptually, I'm thinking of the Library as the set of Struts GA
releases that are dependant on Action and work with a given Action GA.
(So, technically, right now, that's a null set, since we have no GA
releases, but we should at least prime the pump. )
In the future, if we wanted to a tag for that set, we might have to
use a "working copy" tag, since it probably would not be a tag against
the HEAD, but against some GA tag for each of the different
subprojects. It would be a mix of revisions.
* http://svnbook.red-bean.com/en/1.1/ch04s06.html#svn-ch-4-sect-6.2
Though, the Action Library release manager would not need to obtain
the set of source file as a matter of course. No more than we need to
obtain the source for a Commons JAR. The release manager for an Action
Library would only need to test the JARs already decreed GA, the same
as we do for Commons JARs.
My question would be whether we are going to expect an Action Library
release manager to go through the work of making a complex tag?
If someone wants to check-out the Struts source for each of the JARs
and create the tag, that's great, and it would be a good idea to have
a cannonical place to put such a tag. But being a release manager is
hard enough without making work. If someone needs the set, the set is
obtainable. If we need it, then we can create it when we need it, and
save it somewhere so someone doesn't need to create it again. But
creating it up front seems like busy-work.
-Ted.
On 2/17/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 2/17/06, James Mitchell <[EMAIL PROTECTED]> wrote:
Did we tag every subproject? Including 'current'? Maybe I just
missed it.
I didn't see a tag for current... but there is no trunk/branches/tags
directory structure there, either.
It seems to me that we need a tag for (something like)
ACTION-LIB_1.3_00, so you can grab all the "right" versions of the
sub-projects that go with a particular library distribution. These
are the ones we've tested to make sure they work together. I'm just
not sure where to put it. What about in struts/action/tags or just
struts/tags ? Current doesn't seem like the right place, no one would
go looking in "current" for an old release.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
