Hi Stephen,

On Monday 06 March 2006 07:07, Stephen Colebourne 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

Does CLI fit into the picture? Or do you feel that there are issues with it 
that would prevent it from becoming part of the proposed JLC?

> I currently believe these are related, but out of scope:
> [beanutils] - logging is an issue
> [pool] - is pooling more J2EE than J2SE
> [oro]/[regexp] - specialised knowledge
> [math] - specialised, has dependencies
>
> Jakarta Language Components will:
> - develop multiple independent components
> - each component will have no dependencies
> - each component will have no configuration
> - each component provides an extension to the J2SE
> - code judged by would it be out of place in the J2SE
> - a component typically has a broad API (many callable methods)
> - each method typically does relatively little processing
> - have mailing lists (user/dev/commit)

I think the project should continue to have just user and development mailing 
lists, unless list traffic gets to such a point where people are complaining 
of the volume.

If you take Linux, for example, it's a very large project with a very high 
volume mailing list encompassing all disparate concerns in the Linux kernel. 
Maybe the cost of splitting the community mailing lists into many small lists 
is high, and the payoff isn't great?

> - not have a sandbox
> - use jakarta-general (or jakarta-dev?) for cross group issues

Would the JLC be distributed as one jar file? If so, could JLC components 
depend on each other? What are your opinions on distribution issues like 
that?

> Stephen

Thanks.

Regards,
James

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to