[
https://jira.codehaus.org/browse/MEJB-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359912#comment-359912
]
Karsten Tinnefeld commented on MEJB-33:
---------------------------------------
There are good reasons to drop application servers entirely, see e.g.
http://de.slideshare.net/ewolff/java-application-servers-are-dead . There are,
however, a lot of active enterprise applications using application servers and
even EJB working as WebService clients, however clever that may be. Think of
any other more adequate workload JARs the implementation might need instead.
Maven brings about and to perfection the one artifact one description policy
which gives good reasons to have different poms once you need two artifacts -
one to deploy on an appserver and one to work as its client.
There is however this nasty little option to the maven-ejb-plugin which does
not work properly - either it should be repaired or removed entirely to prevent
ill-usage as described above.
So, the requirement is still: build a proper EJB jar AND provide an easy not so
much overhead consistent enterprise-ready (50+ poms) way to create an EJB
client jar using maven, where the client jar dependencies are a small subset of
the EJB jar dependencies.
BTW: sorry for the api mishap accountable to an "update the example in half an
hour on a Sunday eve" action. Please refer to the original example for
consistency's sake.
> 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)
