[
https://issues.apache.org/jira/browse/GERONIMO-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Miller updated GERONIMO-6449:
-----------------------------------
Component/s: Java EE 7
> Java EE 7 API jar files
> -----------------------
>
> Key: GERONIMO-6449
> URL: https://issues.apache.org/jira/browse/GERONIMO-6449
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Java EE 7
> Reporter: Kevin Sutter
> Labels: javaee
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
