Hi,
the recent change in CVS structure means you cannot use the
same module (was: jboss-all) for any branch/revision.
If you checkout e.g. some revision of Branch_3_2 you must use
the module jboss-3.2 (as some relevant cvs metadata cannot
be versioned).
What your question refers to is the difference of the
last revision of a specific branch (e.g. -r Branch_3_2) to
a special release (e.g. -r JBoss_3_2_0_1).
This distinction is still valid (with a Branch being more
like a "work in progress" than a released version).
For the released version you *had to* write:
"cvs co -r JBoss_3_2_0_1 jboss-all"
and for the latest revision on the branch you had to write:
"cvs co -r Branch_3_2 jboss-all"
As of the recent change *now* you must use:
"cvs co -r JBoss_3_2_0_1 jboss-3.2"
for the released version and:
"cvs co -r Branch_3_2 jboss-3.2"
for the latest revision on the branch.
But in each case you still need the correct branch/revision;
you cannot do
"cvs co jboss-3.2"
because you would have the metadata of 3.2 with the files of head.
If you did, you would get exactly the error message which
was started this (mail-)thread.
I hope I got everything correct and did more
of a clarification than an obfuscation :-)
Regards
Michael
Guy Rouillier wrote:
Could you clarify something? This is really a CVS question, not a JBoss
one. When using CVS in general, I've always checked out a specific tag.
For example, the last time I built JBoss 3.2, I checked out revision
JBoss_3_2_0_1, which built without error. I'm guessing that checking out
the branch will always get you the latest revision on that branch, whether
it is tagged with a revision number or not. If that is true, wouldn't it be
safer to check out a particular revision rather than a branch? The latest
version of a file in a particular branch may be a "work in progress", while
hopefully if someone took the time to tag a file with a specific revision
tag, that revision is in some kind of end state.
----- Original Message -----
From: "Adrian Brock" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 17, 2002 1:41 PM
Subject: Re: [JBoss-user] building jboss-3.0 or jboss-3.2 from cvs
http://www.mail-archive.com/jboss-development@;lists.sourceforge.net/msg30843
.html
Regards,
Adrian
From: Joe Phillips <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] building jboss-3.0 or jboss-3.2 from cvs
Date: 17 Oct 2002 13:16:51 -0400
On Thu, 2002-10-17 at 11:34, [EMAIL PROTECTED] wrote:
If I check out jboss-head with cvs I can enter the build directory
and
run the build.sh command and the project builds. How ever if I do the
same with the jboss-3.0 or jboss-3.2 branches they will not build and
both give the same error message.
BUILD FAILED
file:C:/cygwin/home/Administrator/jboss/jboss-3.2/build/../tools/etc/buildf
ragme
nts/tools.ent:29: taskdef class xdoclet.modules.jmx.JMXDocletTask
cannot
be found
I've been getting the same errors from HEAD for a week or more now. I'm
pretty new to JBOSS and so have been lurking, assuming it will either
fix itself soon or someone would complain. You appear to be that
someone.
Is there a step I am missing I am missing for these branches or do i
need
to use a flag on the end of the build command?
I've tried removing and re-getting the sources and multiple JDKs on
Linux with the same exact error. If you're missing something, so am I.
At one point, I could successfully build HEAD so I assume things are
in-flux right now and will fix themselves. What I've seen on jboss-dev
seems to indicate that the build process is in the middle of changes.
I'd be happy to be corrected as well however. You know what they say
happens when you ASSuME.
Thanks for any help, or for pointing the stupidly obvious that I am
clearly missing.
In the meantime (and the reason I haven't pursued more vigorously) I've
been successfully using a recent binary release for my application
development. You may want to try them first.
-joe
--
Innovation Software Group, LLC - http://www.innovationsw.com/
Business Automation Specialists
UNIX, Linux and Java Training
-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
_________________________________________________________________
Surf the Web without missing calls! Get MSN Broadband.
http://resourcecenter.msn.com/access/plans/freeactivation.asp
-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user