Add support for fewer dependencies in client-jars

As a partial workaround, I found I can add server-only dependencies as optional dependencies to the ejb module. Giving them as mandatory dependencies for any ear module containing the server-ear, the dependencies (and also transitive dependencies, as mentioned above) are worked out fine.

The manifest.mf however, having the classpath added (<configuration><archive> <manifest><addClasspath>true</addClasspath> </manifest></archive></configuration>) still has all server library entries referenced which are not available in client.jar packages (Which is, at least, ugly, but should not lead to trouble except when ill-naming dependency jars or depending on different dependency jar versions in different parts of the system.)

Hey guys I had a lot of issues because of this, some class loading problems because one of my ejb-client was bringing to much unnecesary dependencies it was also very used in several projects so we endend excluding lots of libs everywhere, the work arround works, so could you guys add the workaround at least to usage guide in the site or FAQ, it will save many people a lot of time

Thanks

Hi!

we have run into this problem when using 'ejb-client' in jboss ESB and jboss PAR as well as WAR where all dependencies of the 'ejb' module are included..

i have created a small sample project with an 'ejb', 'ear' and a 'war' (the war is not included in ear)

as a workaround i have tried adding 'exclusions' to the 'ejb-client' - for dependencies only needed on server and if i run

'mvn dependency:tree' (from root folder) it looks ok :

[INFO] ------------------------------------------------------------------------
[INFO] Building war
[INFO] task-segment: [dependency:tree]
[INFO] ------------------------------------------------------------------------
[INFO] [dependency:tree {execution: default-cli}]
[INFO] dk.lenio.maven.ejb.client:war:war:0.1-SNAPSHOT
[INFO] +- dk.lenio.maven.ejb.client:ejb:ejb-client:client:0.1-SNAPSHOT:compile
[INFO] +- javax.servlet:servlet-api:jar:2.5:provided
[INFO] +- log4j:log4j:jar:1.2.15:provided
[INFO] | +- javax.mail:mail:jar:1.4:provided
[INFO] | | - javax.activation:activation:jar:1.1:provided
[INFO] | - javax.jms:jms:jar:1.1:provided
[INFO] - junit:junit:jar:3.8.1:test

but if i run 'mvn clean install' from root folder - the server side jars are included..

1768 05-14-10 09:59 WEB-INF/classes/test/war/TestServlet.class
62983 04-27-09 11:12 WEB-INF/lib/activation-1.1.jar
3792 05-14-10 09:59 WEB-INF/lib/ejb-0.1-SNAPSHOT-client.jar
XX 215885 01-29-10 11:38 WEB-INF/lib/webservices-api-2.0.jar
XX 13051007 01-22-10 11:14 WEB-INF/lib/webservices-rt-2.0.jar
215 04-14-10 12:18 WEB-INF/web.xml

if i cd (change directory) to the 'war' folder and 'mvn clean install' - the jars are excluded :

1768 05-14-10 10:32 WEB-INF/classes/test/war/TestServlet.class
3792 05-14-10 09:59 WEB-INF/lib/ejb-0.1-SNAPSHOT-client.jar
215 04-14-10 12:18 WEB-INF/web.xml

How is depending on a 'ejb-client' supposed to work ?

If someone can write up some text about the workaround, with an example POM configuration, I can add it to the Plugin site.

This is a problem for me as well. Having thought about different ways to solve this I have come to the sad comclusion that it is very difficult to do.

As long as the ejb and ejb-client are two variants of the same artifact, with different classifiers, they share the same POM. When another project uses the client, that project will resolve the transitive dependencies of the ejb-client using this shared POM. To really solve this we would need to have a separate POM for the client.