[
http://jira.codehaus.org/browse/MEJB-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222704#action_222704
]
Dennis Lundberg commented on MEJB-33:
-------------------------------------
If someone can write up some text about the workaround, with an example POM
configuration, I can add it to the Plugin site.
> 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