Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Reply-To: <bloritsch@apache.org>
From: "Berin Loritsch" <bloritsch@apache.org>
To: "'Jakarta Commons Developers List'" <commons-dev@jakarta.apache.org>,
   <nicolaken@apache.org>
Subject: RE: [io] new classes and .compress.* packages from Avalon Excalibur
Date: Tue, 9 Jul 2002 14:54:47 -0400
Message-ID: <007f01c2277a$19203630$ac00a8c0@Gabriel>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3D2B2E13.5090000@apache.org>
Importance: Normal

Nicola, if something is currently an Avalon Component, it needs
to stay in Avalon.  That means that SourceResolver, Cache, XML
Bundle, and such stay.

Only things that are not Avalon components should get moved.
Hopefully that lightens your load a little bit.

> -----Original Message-----
> From: Nicola Ken Barozzi [mailto:nicolaken@apache.org] 
> Sent: Tuesday, July 09, 2002 2:40 PM
> To: Jakarta Commons Developers List
> Subject: Re: [io] new classes and .compress.* packages from 
> Avalon Excalibur
> 
> 
> 
> Henri Yandell wrote:
> > 
> > On Tue, 9 Jul 2002, Nicola Ken Barozzi wrote:
> > 
> > 
> >>Ok, everything compiles, makes jars, examples, and runs tests. Some 
> >>tests fail, on the bzip and tar tests, the rest are ok.
> > 
> > Cool.
> > 
> >>I'm not going to debug the failing tests now, 'cause I have other 
> >>moving to do on other packages ;-)
> > 
> > You plan to use this methodology on all of the code 
> submissions? Stick 
> > the code in without working tests then move onto the next piece of 
> > code?
> 
> Yup ;-)
> 
> That is, if someone fixes it, great.
> If not, after all moves, I'll take a stab at fixing it.
> 
> I just tried the testcases in the original places and they 
> are ok, there 
> is something realted to the changes of packagenames and 
> packages of the 
> testcases themselves.
> 
> >>>In the meantime, I'll move other stuff ;-)
> >>
> >>Now it's time for the thread stuff.
> >>Why not put them in threading project?
> >>Or in lang.thread?
> > 
> > 
> > Lang's trying to avoid new code at the moment until we get to move 
> > over to Commons proper. Then the aim is to look at 
> > Avalon.ThreadContext [or is it Thead? The simpler of the two], 
> > reflection bits from around Commons, 
> Avalon.System/StackIntrospector 
> > and Avalon.Util.StringsUtils.
> 
> Ok good.
> 
> BTW, anyone knows the status of the collections move?
> What's left?
> With all these name changes I have a hard time figuring it out ;-)
> 
> > If you want to get Thread out of Avalon, then I'm +1 on into 
> > Commons.Threading and -1 on into Commons.Lang.
> 
> Ok, cool.
> Will do :-)
> 
> 
> Baxter vs modeller? best guess: modeller supercedes Baxter 
> Cache? best guess: Cache in patterns, and 2 impls CLI?best 
> guess: pleeease can someone look into it ;-) Converter?best 
> guess: becomes part of the transformer thing...any ideas? 
> Sourceresolver, i8n, xmlbundle?best guess: new packages 
> Store?besy guess: move things to simplestore
> 
> geez, so many things to do, and even more to come! :-D
> 
> -- 
> Nicola Ken Barozzi                   nicolaken@apache.org
>              - verba volant, scripta manent -
>     (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:commons-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:commons-dev-help@jakarta.apache.org>
> 


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>