On Sun, 2006-03-12 at 23:32 +0100, Andrew C. Oliver wrote:
I'd like to note my opposition. I don't have the same vision as you do
and do not wish to be distracted by 100 irrelavant emails a day about
Commons ABCD.
I'm glad Henri posted that reorganization things were being discussed.
On Mon, 2006-03-13 at 23:48 +0100, Andrew C. Oliver wrote:
that'd only leaves POI in jakarta
did you have a point there? :-)
thanks for highlighting my bad grammar (it's past my bed time)
the point was the bit you snipped :)
preserving jakarta as a special umbrella for poi seems more than
On Wed, 2006-03-08 at 00:09 -0500, Sandy McArthur wrote:
spam
I wrote a GreaseMonkey user script to help me manage the mail on the
Jakarata mailing lists and thought I'd share because I noticed a good
number of people here email from Gmail. If this is completely
inappropriate to post here let
On Tue, 2006-03-07 at 22:20 +0100, Thomas Dudziak wrote:
As a side note, perhaps this is an opportunity to evaluate if there
are better homes for some of the components ? E.g.
betwixt/digester/jxpath could benefit from going to XML commons,
xml tends to be about nuts and bolts. not really
On Tue, 2006-03-07 at 23:07 +0100, Thomas Dudziak wrote:
On 3/7/06, Henri Yandell [EMAIL PROTECTED] wrote:
DbUtils and DBCP to db.apache.org sounds like a win to me; DBCP would
point back to Jakarta for a dependency on [pool], but that helps to foster
intra-project involvement.
In terms of finding homes, I wonder if we should have a root directory under
which we have inactive codebases. One problem would be that no PMC would be
responsible. Or we could create a sort of reverse incubator: a curatorship,
where no active development takes place, but where oversight
I know Jakarta Commons isn't a TLP but considering the
commons.apache.org space is vacant how about addins a blurb about the
Jakarta Commons.
It's the convention that you use your domain as your package. The
Jakarta Commons code is in the package org.apache.commons, not
