great I love to have such things tracked in a tool and not in mailing threads. But this raises an other question, how to get access. Even if I'm logged in java.net I can't access JIRA.
@Anatole: have you the administration rights?
I do have an interesting behavior. If I click on "issue tracking" (after having logged in) on the money entry page in java.net I get to JIRA and there the meassage "your not logged in". So I click on login on JIRA getting back to java.net and there the message "You are already logged in" :-). Any idea?
On 31.01.2013 17:32, Tresch Anatole (KFSC 225) wrote:
I have defined the components in JIRA as for me should make sense. Feel free to give feedback. In short I’ve defined the following components:
build and quality improvement
RI: Basic RI
RI: JDK Adaptations
spec: specification (Lead: atsticks)
As 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 ;-)
Afterwards we have to define also the features and requirements and assign them to the components. Any support in this area is quite welcome!
By the way: the ongoing renewal ballot for this JSR looks good so far. This should allow us to continue effectively with our work.
CREDIT SUISSE AG
Information Technology | Java Core Framework & Support, KSXK 23
Zollstrasse 20/36 | 8070 Zürich | Switzerland
Phone +41 44 334 03 89
JSR 347, "Data Grid" which also is among the few JSRs with a Twitter handle btw., released this call on Google Groups: https://groups.google.com/forum/?fromgroups=#!topic/jsr347/D5-KATaXrzI
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 close enough)
- TCK (tbd, there is no module yet)
There may of course be logical areas like
feel free to suggest something you think is important enough to form a "feature" or "component" right now.
-- Sascha Freitag v/o Dunschtig
[JSR-354] Re: Components