maven-ear-plugin | 易学教程

How to proceed with ear build in maven2?

阅读更多关于 How to proceed with ear build in maven2?

问题 I very new to maven2. Till yesterday i was successful in building war from maven2. My next target is to build ear file for a war file including few of jar files as well. Can you please help with that. I would be greatly thankful. Regards Gnash-85 回答1: The official documentation of the Maven EAR plugin and in particular the section about EAR Modules, the examples and the Usage page should be the reference. But you might find Because I always forget how to use maven-ear-plugin an easier

Maven: How to add files to the root inside an EAR with maven-ear-plugin?

阅读更多关于 Maven: How to add files to the root inside an EAR with maven-ear-plugin?

问题 I need to add 2 XML files inside an EAR generated with maven-ear-plugin. Unfortunately, I haven't seen a way to add an arbitrary file to an EAR; the documentation of the plugin which reads "The EAR plugin supports the following artifacts: ejb, war, jar, ejb-client, rar, ejb3, par, sar, wsr and har". There's nothing for adding a regular file. org.apache.maven.plugins maven-ear-plugin 2.3.1 foo foo 1.4 lib ${parent.groupId} foo-web /foo org.richfaces.framework richfaces-api commons-lang commons

Maven: No marketplace entries found to handle castor, antrun, and ear plugins

阅读更多关于 Maven: No marketplace entries found to handle castor, antrun, and ear plugins

问题 I am importing a maven project into Eclipse. I have the m2e plugin installed and it is pointing to maven 2.2.1 on my machine. I am getting these three errors: No marketplace entries found to handle castor-maven-plugin:1.0:generate in Eclipse No marketplace entries found to handle maven-antrun-plugin:1.1:run in Eclipse No marketplace entries found to handle maven-ear-plugin:2.3.1:generate-application-xml in Eclipse Any resources provided would be greatly appreciated. Thanks 回答1: You can define

Invalid packaging for parent pom.xml, must be “pom” but is “ear”

阅读更多关于 Invalid packaging for parent pom.xml, must be “pom” but is “ear”

问题 Could anybody suggest me an solution with the following exception. I am going to create a multi-module project. Parent Project name is LOGICBACKEND child project name is DBAccess I need to have ear file of LOGICBACKEND which should contain DBAccess prjoects jar file. I am getting following exception when i run mav clean install -P Developer . [ERROR]The project com.project1.Database:DBAccess:1.0-SNAPSHOT (C:\Project1\DBAccess\pom.xml) has 1 error [ERROR]Invalid packaging for parent POM com

JBoss EAR deployment order

阅读更多关于 JBoss EAR deployment order

I have 5 EARs that need to be deployed. One of them, local-configuration-ear-0.3.5-SNAPSHOT.ear , is a dependency of all the others, and they require it at deployment time, i.e. local-configuration-ear-0.3.5-SNAPSHOT.ear needs to be deployed first. All 5 of the EARs are located in the deployments folder. I read here that I can use jboss-deployment-structure.xml to manage the order of EAR deployment, but I ran into some issues. The file I made looks like this: <?xml version="1.0" encoding="UTF-8"?> <jboss-deployment-structure> <deployment> <dependencies> <module name="deployment.local

maven-ear-plugin and JBoss AS 7

阅读更多关于 maven-ear-plugin and JBoss AS 7

问题 I am in the process of migrating to JBoss AS 7, and using maven build, seems to me the maven-ear-plugin does not support JBoss AS 7 yet. By default it uses JBoss AS 4. Does this cause problem? I am also still trying to figure out as I go along how to structure my archives, right now having issues related to the changes in the way JBoss AS 7 class loader works. 回答1: I don't think the maven-ear-plugin is JBoss specific. But you have to specify the JavaEE <version>6</version> in your

Invalid packaging for parent pom.xml, must be “pom” but is “ear”

阅读更多关于 Invalid packaging for parent pom.xml, must be “pom” but is “ear”

Could anybody suggest me an solution with the following exception. I am going to create a multi-module project. Parent Project name is LOGICBACKEND child project name is DBAccess I need to have ear file of LOGICBACKEND which should contain DBAccess prjoects jar file. I am getting following exception when i run mav clean install -P Developer . [ERROR]The project com.project1.Database:DBAccess:1.0-SNAPSHOT (C:\Project1\DBAccess\pom.xml) has 1 error [ERROR]Invalid packaging for parent POM com.project1.logic:LOGIC:1.0-SNAPSHOT (C:\Project1\pom.xml), must be "pom" but is "ear" @ com.project1.logic

In Maven2, what's the simplest way to build a WAR and the EAR to contain that WAR in a single POM?

阅读更多关于 In Maven2, what's the simplest way to build a WAR and the EAR to contain that WAR in a single POM?

问题 Situation is pretty straightforward. I have a Java webapp that I'm converting to be built with Maven. At present, the app is built with Ant into a single WAR file, which is then bundled into an EAR with a very simple application.xml. maven-war-plugin and maven-ear-plugin both look pretty straightforward to me, and it appears they're setting me up to be forced to consider the above as two distinct projects, with the WAR project as a dependency of the EAR project. This seems a tad inconvenient,

Removing version number from file name with Maven

阅读更多关于 Removing version number from file name with Maven

问题 I have a project with 5 modules in maven. Right now, when I do a "mvn clean install", it generates an ear containing the two jars, one war and one sar from the other modules. All the file names contain the version, e.g., projectx-ear-2.0.0.ear, projectx-client-2.0.0.jar, etc. I need to rename one of the jars and the final ear to omit the version in the file name. It should look like this: projectx-ear.ear | +-- projectx-client.jar | +-- projectx-misc-2.0.0.jar | +-- projectx-sar-2.0.0.sar | \

In Maven2, what's the simplest way to build a WAR and the EAR to contain that WAR in a single POM?

阅读更多关于 In Maven2, what's the simplest way to build a WAR and the EAR to contain that WAR in a single POM?

Situation is pretty straightforward. I have a Java webapp that I'm converting to be built with Maven. At present, the app is built with Ant into a single WAR file, which is then bundled into an EAR with a very simple application.xml. maven-war-plugin and maven-ear-plugin both look pretty straightforward to me, and it appears they're setting me up to be forced to consider the above as two distinct projects, with the WAR project as a dependency of the EAR project. This seems a tad inconvenient, especially because a profile setting of the WAR project will change for each environment, which seems