Actually I am not using that extension. I had to update it to support type ejb as well as type jar and to use artifacts rather than dependencies to support snapshots.
The problem I am having is as follows: In my web application I reference EJB's and thus I include the EJB client jar in my WAR and that is what shows up in the Eclipse project. When I run I would like to remotely debug the EJB implementations which are included in other deployed EARS. I have included all the source in my source zips from both the home, remote and bean implementation. When I go into Eclipse I can only select the source code that matches class files in the jar files (client) I am using. If I include the ejb jars everything works ok however the implementation and not the client jar is packaged in my war and that is not what I am looking for. I tried to include both the client jar and the ejb jar in the project.xml but it seems you can only have one dependency with the same name in a project XML even if the types are different. I hope this clarifies the issue a little better. Scott Damon Ryan Developer (720) 514-5389 [EMAIL PROTECTED] -----Original Message----- From: Stéphane Nicoll [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 28, 2004 11:58 PM To: Maven Users List Subject: RE: Eclipse Source when EJB's are used Hello, That's because the extension you made (MPECLIPE-60 I guess) does *NOT* download an artifact which has the type EJB. It downloads only JAR artifacts. See my comment on this ticket: http://jira.codehaus.org/browse/MPECLIPSE-60 Regards, Stéphane -----Original Message----- From: Ryan, Scott [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 28, 2004 6:23 PM To: 'Maven Users List' Subject: Eclipse Source when EJB's are used I am trying to include EJB implementation source code in my eclipse projects for web projects that only use the client jars. I have the several web projects that access EJB's via their home and remote interfaces. In the project XML I include a dependency for the jar version of the artifact which resolves to the client jar. I have created source zip files that include both the client code as well as the implementation code. The problem is that when I include the sources in the .classpath entry Eclipse only lets me see the source code for the client jar rather than the implementation code. If I was able to see the implementation code I could set breakpoints and debug within the implementation code. If I include the deployment jar (ejb) then my war is built with the incorrect jar. I extended the eclipse plugin to support downloading of the source code and inclusion into the .classpath. I tried to reference the dependency twice but the system ignores any duplicates. Any input would be appreciated. Here is my sample project.xml with duplicates. <dependency> <groupId>group1</groupId> <artifactId>api-ejb</artifactId> <version>3.0.1.0</version> <type>jar</type> <properties> <war.bundle>true</war.bundle> </properties> </dependency> <dependency> <groupId>group1</groupId> <artifactId>api-ejb</artifactId> <version>3.0.1.0</version> <type>ejb</type> <properties> <eclipse.source>true</eclipse.source> </properties> </dependency> Scott Damon Ryan Developer (720) 514-5389 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
