[
https://jira.codehaus.org/browse/MEJB-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359925#comment-359925
]
Jeroen Ruijgers commented on MEJB-33:
-------------------------------------
I would be nicer if maven automaticly disabled the transitive dependencies for
a ejb-client module.
> Add support for fewer dependencies in client-jars
> -------------------------------------------------
>
> Key: MEJB-33
> URL: https://jira.codehaus.org/browse/MEJB-33
> Project: Maven EJB Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Karsten Tinnefeld
> Assignee: Karl-Heinz Marbaise
> Fix For: more-investigation
>
> Attachments: ejb-client-packaging-problem-2014.zip,
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
