maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karsten Tinnefeld (JIRA)" <j...@codehaus.org>
Subject [jira] (MEJB-33) Add support for fewer dependencies in client-jars
Date Mon, 29 Dec 2014 12:57:10 GMT

    [ https://jira.codehaus.org/browse/MEJB-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359923#comment-359923
] 

Karsten Tinnefeld commented on MEJB-33:
---------------------------------------

Thanks [~hgk.lenio] for pointing that out. Do I read right that neither the ticket nor the
current maven documentation correctly documents now transitive exclusion is correctly declared?

There is still one issue about this. You suggest that in
Project A using EJB client
    --> Project B EJB client
        --> Project B EJB implementation
project A should declare the implementation JARs it would not need. It would be better though
that project B knows which implementation JARs would not be necessary to the client without
having all As in the world to know (and without all As need to change once B's implementation
dependencies change).


> 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)

Mime
View raw message