On 3/7/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote: > 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 > [beanutils] - logging to be removed > > The following are invited to join if their communities desire: > [oro] > [regexp] > [cli] > > Jakarta Language Components mission: > 'Enhancing Java SE' > > 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 JavaSE > - code judged by would it be out of place in the JavaSE > - a component typically has a broad API (many callable methods) > - each method typically does relatively little processing > - have mailing lists (language-user/language-dev) > - not have a sandbox > - use [EMAIL PROTECTED] ML (new) for cross group issues
Could you elaborate a bit on what the physical / visual-to-users differences to the current commons, well, Jakarta sub-project will be ? Will this be a new Jakarta sub-project (and the other commons components will remain in the current commons one) ? Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
