Jump to: navigation, search

Difference between revisions of "JEE Status Meetings/2011-10-06"

(Juno Planning)
(Juno Planning)
 
(3 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 thought SAP could be interested.
+
* Java EE 6 technologies -
* 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)
+
** JCDI?, other Java EE 6 technologies not currently covered?  - Max brought up this possibility..  Chuck thought SAP could be interested.
* WTP Tomcat Adapter can't seem to work with m2e-wtp 's war overlays when doing ""Serve modules without publishing" : (http://stackoverflow.com/questions/7378845/how-to-make-maven-overlays-working-in-eclipse-tomcat-serve-modules-without-publi) I (we) need to investigate why.
+
 
* WTP Tomcat adapter redeploys entire webapp on class change, is it expected? (Answer from Elson/Server Tools: It is expected. Server needs to be restarted for changes to take place.  For some changes, e.g. method changes without changing the method signature, the user can start the server in debug mode to allow jvm hot method replace for picking up new changes. So a server restart is not needed.) Not clear if this is a Tomcat limitation or WTP adapter limitation...
+
* Server Tools / Tomcat adapter improvements
* 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
+
** WTP Tomcat Adapter - problem with m2e-wtp 's war overlays when doing ""Serve modules without publishing"  
* Still want to be able to deploy my own 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)
+
** WTP Tomcat adapter redeploys entire webapp on class change - what can be done to improve?
* Find a way to make such components contribute to classpath resolution in a custom way : 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.
+
** 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
* 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). According to Chuck, this answer has officially changed, and another approach should be taken. Details?
+
** 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)
* We should be able to specify the deployed 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
+
** 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  ====
  
* Project wish list - What can we do better?  What technical issues need to be improved?
+
* Possibilities of m2e-wtp coming to eclipse?  Can we propose an incubating project?  - Konstantin and Chuck will provide samples of proposals,and assist.
 
+
** 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.
+
 
+
* What are the plans for m2e-wtp coming to eclipse?  Can we propose an incubating project?  - Konstantin and Chuck willing to help create proposal
+
  
 
* 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 09:44, 6 October 2011

Attendees

Agenda

Continue discussion where we left off last week, including prioritization and ownership

Juno Planning

Java EE Tools plan
EJB Tools plan

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 flexible component framework capabilities

Important Bugs

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 ?

Minutes