[
http://jira.codehaus.org/browse/MWAR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154426#action_154426
]
Patrick Huber commented on MWAR-107:
------------------------------------
Is it enough to just exclude immediate dependencies or do I have to go trough
the complete tree and exclude dependencies in deeper nested levels too?
A switch to omit all dependencies would be nice, because in our case we have
one common data model which is included in the war anyways and that's all we
need... Adding this feature would probably require changes to the war and ear
plugins. I don't think this could be done in the ejb plugin, that would
probably require another pom for the client only.
We use EJB3, is it possible to move the business-interface to an other project
and in the client omit the ejb-client dependency entirely (leaving the remote
interface inside the ejb project) and then only include the project with the
business-interface, having ensured all required dependencies are present on the
client side already?
> CLONE -Dependency type "ejb-client" includes main ejb-jar in WAR build.
> -----------------------------------------------------------------------
>
> Key: MWAR-107
> URL: http://jira.codehaus.org/browse/MWAR-107
> Project: Maven 2.x War Plugin
> Issue Type: Bug
> Environment: Windows XP SP2, J2SE 5.0
> Reporter: Heinrich Nirschl
> Assignee: Brett Porter
>
> When I specify a dependency as type "ejb-client" for a project whose
> packaging is set to "war", the build includes the main EJB JAR in the
> WEB-INF/lib directory, not the EJB client JAR.
--
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
