[
https://issues.jboss.org/browse/JBASMP-52?page=com.atlassian.jira.plugin....
]
Matías Blasi commented on JBASMP-52:
------------------------------------
Hi James.
First of all thank you for your support.
The answer is YES.
My ear pom has the jbss-as-maven-plugin defined as follows:
<plugin>
<groupId>org.jboss.as.plugins</groupId>
<artifactId>jboss-as-maven-plugin</artifactId>
<version>7.4.Final</version>
<configuration>
<name>mercury-ear</name>
<force>true</force>
</configuration>
</plugin>
And finally, I run:
# mvn jboss-as:deploy in that ear project.
The ear deploy process succeses:
Maven console:
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
...
[INFO] task-segment: [jboss-as:deploy]
[INFO] ------------------------------------------------------------------------
...
[INFO] [jboss-as:deploy {execution: default-cli}]
oct 02, 2013 10:57:30 AM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.3.GA
oct 02, 2013 10:57:30 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.3.GA
oct 02, 2013 10:57:30 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.3.GA
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15 seconds
[INFO] Finished at: Wed Oct 02 10:57:35 ART 2013
[INFO] Final Memory: 23M/246M
[INFO] ------------------------------------------------------------------------
Jboss server log:
INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed
"mercury.ear"
and later executions:
INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced
deployment "mercury.ear" with deployment "mercury.ear"
But no EJB deployment is triggered in JBoss.
Regards,
Matías.
jboss-as:deploy deploys ear but doesn't deploy contained ejb
module
-------------------------------------------------------------------
Key: JBASMP-52
URL:
https://issues.jboss.org/browse/JBASMP-52
Project: JBoss AS Maven Plugins
Issue Type: Bug
Components: deploy
Affects Versions: 7.4.Final
Environment: Linux hostname 3.7.10-gentoo #1 SMP Fri Aug 30 17:01:59 ART 2013
x86_64 Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz GenuineIntel GNU/Linux
Reporter: Matías Blasi
Assignee: James Perkins
I have a simple ear application (build with maven-ear-plugin).
This application contains just a persistence-unit definition (persistence.xml) and a
ejb-module.
The ejb module is another maven build, containing some ejb3, handled with
maven-ejb-plugin.
The ear file is correctly built:
myapp.ear
|
+ META-INF/application.xml
+ lib/allmylibs.jar
+ myejb.jar
When trying to deploy the ear with the jboss-as:deploy, the application is deployed (the
persistence unit deployment logs in server.log), but no ejb is registered, anyway, no
errors in log, and BUILD SUCCESFUL after mvn command.
Finally, an ear file is present under $JBOSS_HOME/standalone/data/content
The strange thing is that if I get that generated ear file, I can succesfully deploy it
through the management console, or by copying it to a folder scanned by a
deployment-scanner (in both cases the ejbs are correctly deployed)
Nothing found in google! :(
I tried with all the plugin version from 7.1.1 to 7.4.
Also a lot of tries with different maven-ear-plugin and maven-jboss-as-plugin
configuration options.... no lucky after two days of work.
Regards,
Matías.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira