Details
Major Description
Based on the discussion on the dev mailing list, creating a set of JIRAs seems to be the best way to get the ball rolling on developing the set of API jars for Java EE 7. I'll create this parent JIRA along with the individual sub-tasks for each of the major Java EE 7 technologies. There have also been several maintenance releases of other JSRs related to Java EE 7. I didn't automatically create sub-tasks for each of these since I'm not positive API updates were required for each of them. We can create those as sub-tasks as needed.
I'm not familiar with the Geronimo version strategy, so I'll let someone else fill those fields in. Also, there doesn't seem to be a javaee7 component identified yet for Geronimo, if somebody can create one of those and assign it to this JIRA.
This will be a group effort. Whatever group needs a particular spec API jar file will probably be the first one to sign up to do the work. But, even with that, there will probably be multiple people or teams verifying or contributing to the end result.
Attachments
1.
|
API jar for JSR 236 - Concurrency Utils 1.0 |
|
Open | Unassigned |
2.
|
API jar for JSR 339 - JAX-RS 2.0 |
|
Open | Unassigned |
3.
|
API jar for JSR 341 - EL 3.0 |
|
Open | Unassigned |
4.
|
API jar for JSR 344 - JSF 2.2 |
|
Open | Unassigned |
5.
|
API jar for JSR 345 - EJB 3.2 |
|
Open | Unassigned |
6.
|
API jar for JSR 346 - CDI 1.1 |
|
Open | Mark Struberg |
7.
|
API jar for JSR 352 - Java Batch 1.0 |
|
Open | Unassigned |
8.
|
API jar for JSR 250 (Common Annotations 1.2 MR2) |
|
Open | Mark Struberg |