[
http://jira.codehaus.org/browse/MEJB-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189610#action_189610
]
Gabriel Guerrero commented on MEJB-33:
--------------------------------------
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
> 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
>
> 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
