have defined the components in JIRA as for me should make
sense. Feel free to give feedback. In short I’ve defined the
you see, currently I only am the owner of the specification
document. So everybody that wants to take over a basic
default component responsibility can ask for ;-)
we have to define also the features and requirements and
assign them to the components. Any support in this area is
the way: the ongoing renewal ballot for this JSR looks good
so far. This should allow us to continue effectively with
Technology | Java Core Framework & Support, KSXK 23
20/36 | 8070 Zürich | Switzerland
Phone +41 44 334 03 89
Werner Keil [mailto:werner.keil@...]
Sent: Wednesday, January 30, 2013 19:06
Subject: [JSR-354] Feature Leads (as seen in JSR 347)
For all those who are official EG Members
of JSR 354 (making it easier with IP and all that stuff,
everyone may contribute, but officially only EG Members are
supposed to add it to the Spec) something similar may be a good
idea here, too.
@Anatole, or anybody (also non-EG
members) on the list, please suggest features or components.
Also good to transfer that into JIRA as soon as the list of
features is known and accepted.
The modules that currently exist could be
a starting point:
- Core + Singleton (I would say semantically
- TCK (tbd, there is no module yet)
There may of course be logical areas
feel free to suggest something you
think is important enough to form a "feature" or
"component" right now.