Berry created MEAR-303:
--------------------------
Summary: Problem when using EJBClient in an EAR
Key: MEAR-303
URL: https://issues.apache.org/jira/browse/MEAR-303
Project: Maven EAR Plugin
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Berry
Hello,
When trying to upgrade the EAR plugin from version 3.1.0 to 3.2.0, I'm running
into a problem with the packaging of an EJB dependency. I've created a sample
project to show the issue. I'm using a 'core' module with EJB packaging and a
web module packaged as a WAR, all wrapped up in an EAR. Additionally, this is a
Camunda project and deployed to a WildFly Camunda instance, version 7.9.0. If I
build the EAR using plugin version 3.1.0, I get the Camunda ejb-client
dependency inside the WAR and everything works just fine. After upgrading to
version 3.2.0 of the EAR plugin, this dependency is missing and it stops
working. That's the only difference I've been able to find in the real project.
I'm not sure if this is a bug or a mistake in the plugin configuration, but
I've not been able to get it to package as I would expect. Any help would be
appreciated!
Here is the sample project:
https://github.com/berryh/CamundaEJBMavenEarPluginBugDemo
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
