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/2011-10-06"
(New page: == Attendees == == Agenda == Continue discussion where we left off last week ==== Juno Planning ==== :[http://www.eclipse.org/projects/project-plan.php?projectid=webtools.jeetools J...) |
(→Juno Planning) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
== Agenda == | == Agenda == | ||
| − | Continue discussion where we left off last week | + | Continue discussion where we left off last week, including prioritization and ownership |
==== Juno Planning ==== | ==== Juno Planning ==== | ||
| Line 14: | Line 14: | ||
Proposed enhancements | Proposed enhancements | ||
| − | * JCDI?, other Java EE 6 technologies not currently covered? - Max brought up this possibility.. Chuck | + | * Java EE 6 technologies - |
| − | * | + | ** JCDI?, other Java EE 6 technologies not currently covered? - Max brought up this possibility.. Chuck thought SAP could be interested. |
| − | * WTP Tomcat Adapter | + | |
| − | * WTP Tomcat adapter redeploys entire webapp on class change | + | * Server Tools / Tomcat adapter improvements |
| − | * | + | ** WTP Tomcat Adapter - problem with m2e-wtp 's war overlays when doing ""Serve modules without publishing" |
| − | * | + | ** WTP Tomcat adapter redeploys entire webapp on class change - what can be done to improve? |
| − | * | + | ** Solve the challenge of there only being Jar, Ear and War support for adapters. If other project/packaging types are introduced *all* servers need to update their logic as it is at the moment. Presents a challenge with for example BPEL project types which have had to introduce their own specific adapter. |
| − | * EVERY file creation during project facet installation should be optional (Think MANIFEST.MF https://bugs.eclipse.org/bugs/show_bug.cgi?id=349575). | + | |
| − | * Adding WTP libraries should be optional too : https://bugs.eclipse.org/bugs/show_bug.cgi?id=349580 | + | * Enhance extension capabilities to flexible component framework |
| − | * | + | ** Improve extensions for component contributions (Ex : ejb-clients jar built on the fly, without the need for a dedicated ejb-client project) (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=330894) |
| − | * | + | ** Improve components classpath resolution extensibility : Ex: I have a web project, depending on an ejb-client component referencing an ejb project in the workspace. Classpath-wise, the web project should only see the interfaces (and/or some selected classes) from the ejb project. |
| − | * "Web" project / facet consolidation https://bugs.eclipse.org/bugs/show_bug.cgi?id=173901 - Konstantin brought up some API policies in WTP that would make such a change very challenging(preserving compatibility) | + | ** EVERY file creation during project facet installation should be optional (Think MANIFEST.MF https://bugs.eclipse.org/bugs/show_bug.cgi?id=349575). |
| + | ** Adding WTP libraries should be optional too : https://bugs.eclipse.org/bugs/show_bug.cgi?id=349580 | ||
| + | |||
| + | * Improve flexible component framework capabilities | ||
| + | ** Need the ability to include/exclude component resources from deployment using ant-like inclusion/exclusion patterns. Currently implemented for overlays in m2e-wtp and JBoss Archive components using URI parameters. https://bugs.eclipse.org/bugs/show_bug.cgi?id=163221 | ||
| + | ** Add naming capability for archiveName for Jars/projects defined in a classpath library (ex: want to export spring-mvc-x.y.z.jar from the maven lib to /web-inf/lib/spring-mvc.jar) : https://bugs.eclipse.org/bugs/show_bug.cgi?id=359385 | ||
| + | ** Current EAR, RAR support in m2e-wtp list all dependencies in .component. That follows Carl's recommendation from (https://bugs.eclipse.org/bugs/show_bug.cgi?id=297777). Improvements needed to allow extensible references using custom revolvers. | ||
| + | |||
| + | * Improve usability | ||
| + | ** "Web" project / facet consolidation https://bugs.eclipse.org/bugs/show_bug.cgi?id=173901 - Konstantin brought up some API policies in WTP that would make such a change very challenging(preserving compatibility) | ||
Important Bugs | Important Bugs | ||
| Line 32: | Line 41: | ||
* Deployed name of an EAR project is ignored during actual deployment : https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918 | * Deployed name of an EAR project is ignored during actual deployment : https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918 | ||
* Micro-optimization : don't call consumedComponent.getRootFolder() twice in FlatVirtualComponent.consumeComponent(...) : https://bugs.eclipse.org/bugs/show_bug.cgi?id=359360 | * Micro-optimization : don't call consumedComponent.getRootFolder() twice in FlatVirtualComponent.consumeComponent(...) : https://bugs.eclipse.org/bugs/show_bug.cgi?id=359360 | ||
| + | * Make sure all projects in WTP (or from adopters) can handle multi-source components correctly (using the defaultRootSource tag newly introduced in SR1)(Fred to open new bugzilla) | ||
==== Other topics ==== | ==== Other topics ==== | ||
| − | * | + | * Possibilities of m2e-wtp coming to eclipse? Can we propose an incubating project? - Konstantin and Chuck will provide samples of proposals,and assist. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
* WTP meetup at EclipseCon europe ? | * WTP meetup at EclipseCon europe ? | ||
| − | |||
** Fred and Max are going. Anyone else ? | ** Fred and Max are going. Anyone else ? | ||
== Minutes == | == Minutes == | ||
Latest revision as of 10:44, 6 October 2011
Attendees
Agenda
Continue discussion where we left off last week, including prioritization and ownership
Juno Planning
Themes: Improved usability, Improved extension capabilities, Maven(m2e) integration
Proposed enhancements
- Java EE 6 technologies -
- JCDI?, other Java EE 6 technologies not currently covered? - Max brought up this possibility.. Chuck thought SAP could be interested.
- Server Tools / Tomcat adapter improvements
- WTP Tomcat Adapter - problem with m2e-wtp 's war overlays when doing ""Serve modules without publishing"
- WTP Tomcat adapter redeploys entire webapp on class change - what can be done to improve?
- Solve the challenge of there only being Jar, Ear and War support for adapters. If other project/packaging types are introduced *all* servers need to update their logic as it is at the moment. Presents a challenge with for example BPEL project types which have had to introduce their own specific adapter.
- Enhance extension capabilities to flexible component framework
- Improve extensions for component contributions (Ex : ejb-clients jar built on the fly, without the need for a dedicated ejb-client project) (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=330894)
- Improve components classpath resolution extensibility : Ex: I have a web project, depending on an ejb-client component referencing an ejb project in the workspace. Classpath-wise, the web project should only see the interfaces (and/or some selected classes) from the ejb project.
- EVERY file creation during project facet installation should be optional (Think MANIFEST.MF https://bugs.eclipse.org/bugs/show_bug.cgi?id=349575).
- Adding WTP libraries should be optional too : https://bugs.eclipse.org/bugs/show_bug.cgi?id=349580
- Improve flexible component framework capabilities
- Need the ability to include/exclude component resources from deployment using ant-like inclusion/exclusion patterns. Currently implemented for overlays in m2e-wtp and JBoss Archive components using URI parameters. https://bugs.eclipse.org/bugs/show_bug.cgi?id=163221
- Add naming capability for archiveName for Jars/projects defined in a classpath library (ex: want to export spring-mvc-x.y.z.jar from the maven lib to /web-inf/lib/spring-mvc.jar) : https://bugs.eclipse.org/bugs/show_bug.cgi?id=359385
- Current EAR, RAR support in m2e-wtp list all dependencies in .component. That follows Carl's recommendation from (https://bugs.eclipse.org/bugs/show_bug.cgi?id=297777). Improvements needed to allow extensible references using custom revolvers.
- Improve usability
- "Web" project / facet consolidation https://bugs.eclipse.org/bugs/show_bug.cgi?id=173901 - Konstantin brought up some API policies in WTP that would make such a change very challenging(preserving compatibility)
Important Bugs
- WTP tomcat adapter likes to remove deployed jars (from the Maven Classpath library) randomly (https://issues.sonatype.org/browse/MECLIPSEWTP-117)
- Deployed name of an EAR project is ignored during actual deployment : https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918
- Micro-optimization : don't call consumedComponent.getRootFolder() twice in FlatVirtualComponent.consumeComponent(...) : https://bugs.eclipse.org/bugs/show_bug.cgi?id=359360
- Make sure all projects in WTP (or from adopters) can handle multi-source components correctly (using the defaultRootSource tag newly introduced in SR1)(Fred to open new bugzilla)
Other topics
- Possibilities of m2e-wtp coming to eclipse? Can we propose an incubating project? - Konstantin and Chuck will provide samples of proposals,and assist.
- WTP meetup at EclipseCon europe ?
- Fred and Max are going. Anyone else ?