This wasn't a code change, it was a change to how jboss is checked out from cvs. I think maybe Jason forgot that there is no branching available in CVSROOT.
Basically the problem is that cvs sucks. I think the solution is to have jboss-all-3_0, jboss-all-3_2, and jboss-all-4_0 targets that check out the appropriate structure for each release. We won't change the production targets, newer ones can be subject to improvement. david jencks On 2002.10.07 15:19:40 -0400 Bill Burke wrote: > All and all I think big structural changes and any big code changes, or > any > big features should be forbidden from being added to a production branch. > IMHO, they shouldn't be allowed for any branched version as a branch > means > we are trying to stabalize. > > BTW, you've really hosed me so fix it! > > Bill > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of > Scott > > M Stark > > Sent: Monday, October 07, 2002 2:58 PM > > To: [EMAIL PROTECTED] > > Cc: Jason Dillon > > Subject: Re: [JBoss-dev] README :: Thirdparty structure changed > > > > > > This has broken the existing 3.0 and 3.2 build structures. Fix > > these changes > > immediately as we are not going through the production branch build > > files to accommodate this change. > > > > I also changed the jboss-all alias to checkout its content into > > the jboss-all > > directory as this had been changed to jboss. > > > > xxxxxxxxxxxxxxxxxxxxxxxx > > Scott Stark > > Chief Technology Officer > > JBoss Group, LLC > > xxxxxxxxxxxxxxxxxxxxxxxx > > > > ----- Original Message ----- > > From: "Jason Dillon" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Sunday, October 06, 2002 8:05 PM > > Subject: [JBoss-dev] README :: Thirdparty structure changed > > > > > > > Hi... me again ;) > > > > > > I finally got around to fixing, or rather getting around an > unfortunate > > > side-effect of the CVS 'update' command. The previous behavior > > would cause > > > local clients to download the entire thirdparty/* module (which > > is time and > > > space consuming). > > > > > > CVS is not desgined to handle nested structures very well, so I > > modified the > > > _<project>_thirdparty cvs modules to flatten the directory structure. > > > > > > I also had to update the libraries.ent file to use the new root > > directories > > > for each library. > > > > > > So, what this means to you is that you need to do the following: > > > > > > 1) Re-checkout the project you are working with OR: > > > > > > a) Remove the thirdparty sub-directory > > > > > > b) Check out the _<project>_thirdparty module. So for the > > 'jboss-all' > > > project, you would checkout _jboss-all_thirdparty > > > > > > 2) Ensure that your 'tools' module is up to date. > > > > > > That's it. > > > > > > Unix users working on jboss-all (HEAD) you can execute the > > following from > > > the jboss-all project directory: > > > > > > rm -rf thirdparty > > > cvs get _jboss-all_thirdparty > > > cvs update tools > > > > > > Let me know if you have any questions, comments or problems. > > > > > > Please no flames *whimper*... > > > > > > --jason > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
