Ah I see "Actually subclipse can be used with Eclipse 2.1.0 and 2.1.1." on http://subclipse.tigris.org/. Bummer they do not support the current 3.0.m version.
Gary > -----Original Message----- > From: Gary Gregory [mailto:[EMAIL PROTECTED] > Sent: Friday, December 19, 2003 19:15 > To: 'Jakarta Commons Developers List' > Subject: RE: [codec] [proposal] Moving To Apache Commons > > > -----Original Message----- > > From: Tim O'Brien [mailto:[EMAIL PROTECTED] > > Sent: Friday, December 19, 2003 18:56 > > To: [EMAIL PROTECTED] > > Subject: [codec] [proposal] Moving To Apache Commons > > > > Codec, a small - probably the smallest - piece of code in Jakarta-land. > > Is well suited for inclusion in Apache Commons. I propose that Codec be > > used as a guinea pig of sorts to test the waters of Apache Commons. It > > is not language specific, and it is something that could be excised from > > the Commons with limited fuss. > > > > To this end, I propose that Jakarta Commons Codec be officially > > transformed into Apache Commons Codec. > > +1. > > > > > Simultaneous with the move from J-C to A-C - > > > > #1. Commons Codec will be hosted on Subversion > > -1, unless I can use Eclipse to access the repos. Can Subversion work in > some kind of CVS compatibility mode? Using a CLI is such a pain. > > > > > Why? Subversion is ready and superior in almost every aspect. Moving > > smaller projects such as this one to Subversion will allow us to iron > > out any kinks, and will help nudge more projects in this direction. > > > > #2. Commons Codec will use Jira for issue tracking. > > Is there any reason to use a normally commercial product here? [Same > issues > as using Clover I guess] Are folks sick of bugzilla? Not perty enough? > Curious, > Gary > > > > > #3. All committers to Commons Codec are also granted access to Apache > > Commons > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED]
