Difference between revisions of "JEE Status Meetings/2011-09-29"

Revision as of 05:46, 29 September 2011

Attendees

Agenda

Juno Planning

Java EE Tools plan

EJB Tools plan

Proposed enhancements - I will work on assigning bugzilla's new or existing

• Make sure all projects in WTP (or from adopters) can handle multi-source components correctly (using the defaultRootSource tag newly introduced in SR1)
• 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?
• 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
• 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)
• 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.
• 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
• Bug : WTP tomcat adapter likes to remove deployed jars (from the Maven Classpath library) randomly (https://issues.sonatype.org/browse/MECLIPSEWTP-117)
• 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?
• 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
• Deployed name of an EAR project is ignored during actual deployment : https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918
• "Web" project / facet consolidation https://bugs.eclipse.org/bugs/show_bug.cgi?id=173901
• Micro-optimization : don't call consumedComponent.getRootFolder() twice in FlatVirtualComponent.consumeComponent(...) : https://bugs.eclipse.org/bugs/show_bug.cgi?id=359360

Other topics

• Project wish list - What can we do better? What technical issues need to be improved?

• • 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.

• WTP meetup at EclipseCon europe ?

• • Fred and Max are going. Anyone else ?

Minutes