commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell" <flame...@gmail.com>
Subject Re: [all] Proposal: Jakarta Language Components
Date Mon, 06 Mar 2006 15:54:09 GMT
On 3/5/06, Stephen Colebourne <scolebourne@btopenworld.com> wrote:
> Time to stop being negative, here is what I would like to happen next.
>
>
> I hereby propose the creation of a new Jakarta entity named 'Jakarta
> Language Components'.
>
> This will be formed from the following codebases:
> [lang]
> [io]
> [collections] - expected to divide
> [primitives]
> [codec]
> [id] - on exit from sandbox
> [convert] - if ever developed
>
> I currently believe these are related, but out of scope:
> [beanutils] - logging is an issue

If logging were removed?

> [pool] - is pooling more J2EE than J2SE

Not sure. Should we also consider a J-JEE-C? With this being J-JSE-C?
[pool], [dbcp] and [JCS] all seem related.

> [oro]/[regexp] - specialised knowledge

This is a hard one. Specialised yes, but definitely a JLC fit and
otherwise we'll just have a Jakarta Regexp Components group.

> [math] - specialised, has dependencies

It's not a fit anyway - [math] goes way, way beyond the JDK.

Others:

[bcel]? Again a specialized knowledge one.

[dbutils]? Do we consider jdbc to be JEE?
[email]? JEE?

It might make things simpler to draw up an entire future re-org of
Jakarta. See who gets dropped through the cracks and decide if we have
to kill, accept or leave them to stand alone. There are some obvious
ones for JWC, and some that just don't seem to fit and would have to
stand alone.

Hen

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


Mime
View raw message