maven-ear-plugin

Removing version number from file name with Maven

梦想与她 提交于 2019-12-02 21:39:25
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 | \-- projectx-web-2.0.0.web Right now I'm using the following plugins to build: maven-compiler-plugin and

How do I upgrade the version of a maven plugin?

房东的猫 提交于 2019-12-02 15:35:54
I am using the maven-ear-plugin version 2.3.1 - I know there is a new version available: http://maven.apache.org/plugins/maven-ear-plugin/ I can't work out how to upgrade to the latest version? andri The default plugin versions are inherited from the Super POM, and you can check them with mvn help:effective-pom . If you want to override the version provided there, add this to your POM: <project> <build> <plugins> <plugin> <artifactId>maven-ear-plugin</artifactId> <version>2.3.1</version> </plugin> </plugins> </build> </project> Replace the version with what you need. Pat Even though this has

How to manipulate Manifest file with maven

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-02 06:31:07
问题 I have an EAR file built with maven. The EAR contains several jars and I need to add a line in the manifest file for just one of these jars. I know of the maven-jar-plugin option (manifestEntries) but this is good for a single standalone jar, not one that is inside an EAR. 回答1: If you take a deeper look into maven-ear-plugin configuration you will find the archive configuration part which is exactly intended for such purposes. This can be added to the configuration of the maven-ear-plugin:

How to manipulate Manifest file with maven

岁酱吖の 提交于 2019-12-02 00:59:51
I have an EAR file built with maven. The EAR contains several jars and I need to add a line in the manifest file for just one of these jars. I know of the maven-jar-plugin option (manifestEntries) but this is good for a single standalone jar, not one that is inside an EAR. If you take a deeper look into maven-ear-plugin configuration you will find the archive configuration part which is exactly intended for such purposes. This can be added to the configuration of the maven-ear-plugin: <archive> <addMavenDescriptor/> <compress/> <forced/> <index/> <manifest> <addClasspath/>

maven-ear-plugin and JBoss AS 7

北城余情 提交于 2019-12-01 20:07:20
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. Thor I don't think the maven-ear-plugin is JBoss specific. But you have to specify the JavaEE <version>6</version> in your configuration: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-ear-plugin</artifactId>

How to remove version number from war file

蹲街弑〆低调 提交于 2019-11-30 23:00:21
I have a Dependency in child pom like this. <dependencies> <dependency> <groupId>sample-groupID</groupId> <artifactId>sfint</artifactId> <version>1.0.0-SNAPSHOT</version> <type>war</type> </dependency> </dependencies> And I am using maven-ear-plugin. <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven.ear.plugin</artifactId> <version>2.10</version> <configuration> <modules> <webModule> <groupId>sample-gropuID</groupId> <artifactId>sfint</artifactId> <version>1.0.0-SNAPSHOT</version> <moduleID>WebModule_sfint</moduleID> <bundleFileName>sfint.war</bundleFileName> <

Building EAR from a single Maven project

烂漫一生 提交于 2019-11-28 14:32:57
There is a Maven project that used to have JAR packaging type. Now the project has evolved, and it is required that it be built as EAR, including the JAR proper and its dependencies altogether. Does it necessarily mean I have to introduce the second POM with EAR packaging type? Is it possible to build JAR+EAR from a single Maven project? The reason behind that is that I don't really want to radically reorganize my repository structure. If not possible, I guess I'd need to somehow reorganize project structure to make use of Maven modules. What (sub)module structure would you recommend in that

How to add WAR inside EAR with Maven

前提是你 提交于 2019-11-28 04:33:47
I have EAR with an application and I need to extend this app with my own code that is packaged as a WAR. Is there a maven plugin that can help me with putting the WAR inside the EAR? The manual procedure is to put WAR inside EAR and add module to application.xml. I would like to automate that. EDIT: small clarification - the WAR project is using maven but for EAR I have only the binary file nothing more. I'd create a new module that has <packaging>ear</packaging> . In the dependencies for this ear module, include your war module: <dependency> <groupId>com.your.group.id</groupId> <artifactId

Create complete EAR Project with Maven and Eclipse Helios

孤街醉人 提交于 2019-11-27 19:49:30
I read some articles about how to set up eclipse and maven to create a new empty ear project but all solutions weren't complete or are to old. I believe that I need to create three pom.xml files / or three projects: client project with the WEB-APP structure (like a regular dynamic web project). This should result in a WAR file. server project with the ejbs. This should be a JAR file. ear project which joins both projects together. I tried that with help of the integrated maven plugin in eclipse. Since (I believe Helios) maven is already integrated in eclipse. So I go to file -> new -> maven ->

Building EAR from a single Maven project

给你一囗甜甜゛ 提交于 2019-11-27 08:40:22
问题 There is a Maven project that used to have JAR packaging type. Now the project has evolved, and it is required that it be built as EAR, including the JAR proper and its dependencies altogether. Does it necessarily mean I have to introduce the second POM with EAR packaging type? Is it possible to build JAR+EAR from a single Maven project? The reason behind that is that I don't really want to radically reorganize my repository structure. If not possible, I guess I'd need to somehow reorganize