You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hans Guldager Knudsen (JIRA)" <ji...@codehaus.org> on 2010/05/14 10:42:13 UTC

[jira] Updated: (MEJB-33) Add support for fewer dependencies in client-jars

     [ http://jira.codehaus.org/browse/MEJB-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans Guldager Knudsen updated MEJB-33:
--------------------------------------

    Attachment: ejb-client-packaging-problem.zip

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 ?




> Add support for fewer dependencies in client-jars
> -------------------------------------------------
>
>                 Key: MEJB-33
>                 URL: http://jira.codehaus.org/browse/MEJB-33
>             Project: Maven 2.x EJB Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.1
>            Reporter: Karsten Tinnefeld
>         Attachments: ejb-client-packaging-problem.zip
>
>
> Given a scenario, where several application tiers are installed on different servers, are realized as EJB3 applications, and packaged using maven.
> When configuring an ejb module, I give dependencies to all dependency jars that are used to implement the features. However, they are currently all added as dependency to the client-jar artifacts as well, so that unused libraries are deployed on client servers.
> I'd like to mark dependencies as server-jar only, e.g. by an clientJarExclusions configuration element to the plugin, which takes a set of exclusion elements like the exclusions-element in a dependency. These dependencies should behave as compile-scope in the server- and provided-scope in the client-jars. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira