Okay, I've moved stuff around and setup an SVN externals checkout. Let me know if this fulfills the need to keep the code in 'standard'.
-Nathan > -----Original Message----- > From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] > Sent: Sunday, September 10, 2006 6:12 PM > To: harmony-dev@incubator.apache.org > Subject: [classlib][concurrent] We need to get the concurrent code out of > the 'enhanced' part of SVN > > Nathan, > > ... because that part of SVN implies that we have the provenance > documentation for the code that makes it in there. > > For concurrent, we don't, so it has to go out. > > Please move it to standard/classlib/trunk/modules/concurrent or something. > > Given it's stablity - that it doesn't change in our SVN - it should be a > minor problem to simply have some simple build script that compiles and > jars the code, and puts the jar in the enhanced/classlib/trunk area for > build and packaging purposes. > > geir > > --------------------------------------------------------------------- > Terms of use : http://incubator.apache.org/harmony/mailing.html > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
