[
https://issues.apache.org/jira/browse/MEJB-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17966068#comment-17966068
]
Olivier Lamy commented on MEJB-33:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-ejb-plugin#52|https://github.com/apache/maven-ejb-plugin/issues/52].
Please visit the GitHub issue to view further activity, add comments, or
subscribe to receive notifications.
> Add support for fewer dependencies in client-jars
> -------------------------------------------------
>
> Key: MEJB-33
> URL: https://issues.apache.org/jira/browse/MEJB-33
> Project: Maven EJB Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: tinne
> Priority: Major
> Fix For: more-investigation
>
> Attachments: ejb-client-packaging-problem-2014.zip,
> ejb-client-packaging-problem.zip, make-client-separate.patch
>
>
> 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
(v8.20.10#820010)
