Tags are with respect to the JBoss release, not unique for the invidual modules.
There needs to be a 2.4 branch of the jbosscx module with internal release
tags heading to a JBoss_2_4_0 release tag for the version of jbosscx that is
included in the JBoss 2.4.0 release.
----- Original Message -----
From: "Jason Dillon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 20, 2001 4:10 PM
Subject: Re: [JBoss-dev] Fixed very small problem with ConnectionFactoryLoader
> > Follow the steps detailed on the web site, i.e. add a tag to the
> > jboss module when you update the jar file. Add a tag with the same
> > name to the jbosscx module when you do this.
>
> Please excuse me if I am missing something obvious, but I don't quite get
> what I need to do. I looked at the tags on a file in jbosscx:
>
> cvs status -v build.sh
> ===================================================================
> File: build.sh Status: Up-to-date
>
> Working revision: 1.1.1.1
> Repository revision: 1.1.1.1 /cvsroot/jboss/jbosscx/src/build/build.sh,v
> Sticky Tag: (none)
> Sticky Date: (none)
> Sticky Options: (none)
>
> Existing Tags:
> JBoss_2_2_1 (revision: 1.1.1.1)
> Branch_2_2 (branch: 1.1.1.1.2)
> JBoss_2_2_0_Final (revision: 1.1.1.1)
> JBOSSCX_0_2 (revision: 1.1.1.1)
> start (revision: 1.1.1.1)
> jboss (branch: 1.1.1)
>
> And I seed a JBOSSCS_0_2 tag, thats fine, but I don't see any tag on the
> jbosscx-0.2.jar file in jboss:
>
> cvs status -v jbosscx-0.2.jar
> ===================================================================
> File: jbosscx-0.2.jar Status: Up-to-date
>
> Working revision: 1.7
> Repository revision: 1.7
> /cvsroot/jboss/jboss/src/lib/jbosscx-0.2.jar,v
> Sticky Tag: (none)
> Sticky Date: (none)
> Sticky Options: -kb
>
> Existing Tags:
> Rel_3_0_0_0 (revision: 1.7)
> Rel_2_5_0_0 (revision: 1.7)
> Rel_2_4_0_0 (revision: 1.7)
> Branch_2_4 (branch: 1.7.4)
> Rel_2_3_1 (revision: 1.7)
> RabbitHole (branch: 1.7.2)
> JBoss_2_2_2 (revision: 1.3.2.2)
> JBoss_2_2_1 (revision: 1.3)
> Rel_2_2_1 (revision: 1.3)
> JBoss_2_2_0_Final (revision: 1.3)
> Rel_2_2_0 (revision: 1.3)
> Branch_2_2 (branch: 1.3.2)
> Rel_2_3_0 (revision: 1.3)
>
> So, what I *think* I should do is to either update the JBOSSCX_0_2 tag to
> the current HEAD of jbosscx, or create a JBOSSCX_0_2_1, though it seams like
> this number will grow as minor changes are added. Either way, tag the
> entire jbosscx module, then check the jbosscx.jar into jboss, and tag only
> that file with the same tag.
>
> Is this about it, or am I am missing something? I briefly scanned
> CVSAdmin.jsp for information/examples about modules but did not see
> anything.
>
> --jason
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
