Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JEE Status Meetings/2008-07-16"
(New page: == Attendees == * Kaloyan Raev * Chuck Bridgham * Carl Anderson * Konstantin Komissarchik == Agenda == # Mixing spec level versions in EAR == Minutes == The discussion was triggered i...) |
|||
| Line 17: | Line 17: | ||
WTP support for Java EE 5 modules in a 1.4 level EAR is too big to contain in a maintenance release- will be a line item for WTP 3.1. | WTP support for Java EE 5 modules in a 1.4 level EAR is too big to contain in a maintenance release- will be a line item for WTP 3.1. | ||
| + | |||
| + | It was agreed that we should allow this scenario however... (Java EE Modules contained in J2EE 1.4 applications) | ||
| + | Chuck mentioned possibly using the facet identifier to allow this scenario (leaving the xml namespace version alone), but the consensus on the call was | ||
| + | to allow this without changing the facet version, which spawned a separate topic - should be considering spec migration in future release. | ||
| + | |||
| + | We also need to consider how we present the capabilities of the targeted runtime - via deployment validation - possibly another line item. | ||
| + | Not all runtimes may be able to handle this scenario, and existing facet/runtime enablement doesn't cover this amount of detail. | ||
| + | |||
| + | Many areas need to be tested for this change, such as validation, deployment, Ear assembly editing in project property sheet etc.... | ||
Latest revision as of 09:45, 18 July 2008
Attendees
- Kaloyan Raev
- Chuck Bridgham
- Carl Anderson
- Konstantin Komissarchik
Agenda
- Mixing spec level versions in EAR
Minutes
The discussion was triggered in the wtp-dev mailing list: http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg06224.html
WTP support for Java EE 5 modules in a 1.4 level EAR is too big to contain in a maintenance release- will be a line item for WTP 3.1.
It was agreed that we should allow this scenario however... (Java EE Modules contained in J2EE 1.4 applications) Chuck mentioned possibly using the facet identifier to allow this scenario (leaving the xml namespace version alone), but the consensus on the call was to allow this without changing the facet version, which spawned a separate topic - should be considering spec migration in future release.
We also need to consider how we present the capabilities of the targeted runtime - via deployment validation - possibly another line item. Not all runtimes may be able to handle this scenario, and existing facet/runtime enablement doesn't cover this amount of detail.
Many areas need to be tested for this change, such as validation, deployment, Ear assembly editing in project property sheet etc....