The Apache Maven team is pleased to announce the release of the Apache
Maven EAR Plugin, version 3.3.0
This plugin generates Java EE Enterprise Archive (EAR) file.
https://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration
The Maven team is pleased to announce the release of the Apache Maven EAR
Plugin, version 3.2.0
This plugin generates a J2EE Enterprise Archive (EAR) file.
https://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration
Hi users of Apache Maven,
We are working on MEAR-153 (https://issues.apache.org/jira/browse/MEAR-153)
to implement skinnyModules option for the Maven EAR Plugin.
Refer to https://github.com/apache/maven-ear-plugin/pull/24 for the changes
which can be used to try skinnyModules option which
,
Hervé
Le jeudi 1 octobre 2020, 09:16:12 CEST Martin Höller a écrit :
> Hi!
>
> On 01. Okt. 2020 Hervé Boutemy wrote:
> > The Maven team is pleased to announce the release of the Apache Maven EAR
> > Plugin, version 3.1.0
> With maven-ear-plugin 3.1.0 I get this exception
Hi!
On 01. Okt. 2020 Hervé Boutemy wrote:
> The Maven team is pleased to announce the release of the Apache Maven EAR
> Plugin, version 3.1.0
With maven-ear-plugin 3.1.0 I get this exception on a project that built fine
with 3.0.2:
$ mvn -X install
[...]
[ERROR] Failed to execut
The Maven team is pleased to announce the release of the Apache Maven EAR
Plugin, version 3.1.0
This plugin generates a J2EE Enterprise Archive (EAR) file.
https://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration
2020 17:18
To: Maven Users List ; Bram Patelski
Subject: Re: maven-ear-plugin bundleFileName don't change the name of the war i
want to bundle with the ear
Hi,
On 04.06.20 14:17, Bram Patelski wrote:
> You can use the finalName property in the build-section of the Maven
> po
/questions/14488509/maven-how-to-rename-the-war-file-for-the-project
PGP key:
https://keys.mailvelope.com/pks/lookup?op=get=0xF31094A567CE732E
On Wed, Jun 3, 2020 at 9:44 PM Meir Yanovich
wrote:
im using the latest version of the maven-ear-plugin
i like to bundle the test.war into my ear
PM Meir Yanovich
wrote:
> im using the latest version of the maven-ear-plugin
> i like to bundle the test.war into my ear
> but the output is always :
>
> test1-test21999.test-SNAPSHOT.war
>
> which is always the default :
>
> outputFileNameMapping = @{groupId
im using the latest version of the maven-ear-plugin
i like to bundle the test.war into my ear
but the output is always :
test1-test21999.test-SNAPSHOT.war
which is always the default :
outputFileNameMapping =
@{groupId}@-@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@
how do i
not
un-append artifacts from the project build, should it?
Ben
Am Mo., 3. Feb. 2020 um 11:08 Uhr schrieb Benjamin Marwell :
>
> Hi all,
>
> since today my ear-plugin configuration does not work anymore and
> stops with an exception.
>
> I pull in a dependency (type war
Hi all,
since today my ear-plugin configuration does not work anymore and
stops with an exception.
I pull in a dependency (type war) from another module in the same
reactor. I also pull the same dependency in again with a classifier
and another type to be used with the maven-assembly-plugin
on of the artifact. The no-version-for-ejb means
> the filename is the artifactId without the version in case of EJB type.
>
>
> Are you looking for something like that?
>
>
> Kind regards
> Karl Heinz Marbaise
>
>
>
> On 20/06/17 19:21, Eric B wrote:
>
>> Is
type.
Are you looking for something like that?
Kind regards
Karl Heinz Marbaise
On 20/06/17 19:21, Eric B wrote:
Is there a way to customize the filename used by the maven-ear-plugin for
the different modules but in a general template way?
At the moment, the bundleFilename by default seems
Is there a way to customize the filename used by the maven-ear-plugin for
the different modules but in a general template way?
At the moment, the bundleFilename by default seems to be:
${artifactId}-${version}.${packaging}
I would like to prepend it with a $[groupId} as well.
${groupId
The Apache Maven team is pleased to announce the release of the
Apache Maven EAR Plugin Version 2.10.1.
Sorry the link to the plugin was wrong. The link correctly looks like
this:
http://maven.apache.org/plugins/maven-ear-plugin/
Enjoy,
-The Apache Maven team
The Apache Maven team is pleased to announce the release of the
Apache Maven EAR Plugin Version 2.10.1.
This plugin generates Java EE Enterprise Archive (EAR) file. It can also
generate the deployment descriptor file (e.g. application.xml).
http://maven.apache.org/maven-ear-plugin/
Release
The Apache Maven team is pleased to announce the release of the
Apache Maven EAR Plugin, version 2.10
This plugin generates Java EE Enterprise Archive (EAR) file. It can also
generate the deployment descriptor file (e.g. application.xml).
http://maven.apache.org/plugins/maven-ear-plugin/
You
but I'm not sure how to
provide this as it also seems to depend on the infrastructure.
Hm...you say on one side it's a bug of maven-ear-plugin but here you say
different... ?...
As changing the version of the m-ear-p is enough to fix the problem I
really do think it's a bug in the ear plugin
Hi!
I'm using the maven-ear-plugin to create an EAR with a skinny WAR. This
worked fine till I did an update from version 2.9 to version 2.9.1.
The actual problem is quite hard to explain, so I'll try and start with
an abstract and provide details below.
The problem is, the skinny WAR contains
the jars
you don't like to have in your ear as a transitive dependency?
Can you post your pom file ?
On 11/26/14 3:31 PM, Martin Hoeller wrote:
Hi!
I'm using the maven-ear-plugin to create an EAR with a skinny WAR. This
worked fine till I did an update from version 2.9 to version 2.9.1
The Apache Maven team is pleased to announce the release of the
Apache Maven EAR Plugin, version 2.9.1
This plugin (insert short description of the plugin's purpose).
http://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration
I have my plugin configured as:
plugin
artifactIdmaven-ear-plugin/artifactId
version2.9/version
configuration
defaultJavaBundleDirlib//defaultJavaBundleDir
skinnyWarstrue/skinnyWars
Hi!
I see strange behavior when using the maven EAR plugin with the
skinnyWar [1] feature, which might be a bug.
Here is the (simplified) module-structure I have:
core
+-- core-shared
web
+-- backend
+-- war
ee
+-- ear
Usually all modules share the same version (let's say 1.0) number
of things dragged
in with the latest version of otherwise well-written libraries.
Exclusions need to be added to get what you want in your artifacts.
Ron
On 07/02/2014 9:21 AM, Reto Hablützel wrote:
Hi there,
I built an ear using the maven-ear-plugin
in with the latest version of otherwise well-written libraries.
Exclusions need to be added to get what you want in your artifacts.
Ron
On 07/02/2014 9:21 AM, Reto Hablützel wrote:
Hi there,
I built an ear using the maven-ear-plugin (version 2.6
Hablützel wrote:
Hi there,
I built an ear using the maven-ear-plugin (version 2.6).
The ear is configured such that it includes two libraries
into
the lib
folder, both with the same artifactId as well as the same
version
wrote:
Hi there,
I built an ear using the maven-ear-plugin (version 2.6).
The ear is configured such that it includes two libraries
into
the lib
folder, both with the same artifactId as well as the same
version
I confirm that the use case you mention is supposed to work transparently.
This most likely looks like a bug.
Thanks for reporting this.
S.
On Fri, Feb 7, 2014 at 3:21 PM, Reto Hablützel ret...@rethab.ch wrote:
Hi there,
I built an ear using the maven-ear-plugin (version 2.6).
The ear
Hi there,
I built an ear using the maven-ear-plugin (version 2.6).
The ear is configured such that it includes two libraries into the lib
folder, both with the same artifactId as well as the same version, but a
different groupId. Now if I simply call 'mvn package' only the first one is
included
Hablützel wrote:
Hi there,
I built an ear using the maven-ear-plugin (version 2.6).
The ear is configured such that it includes two libraries into the lib
folder, both with the same artifactId as well as the same version, but a
different groupId. Now if I simply call 'mvn package' only the first one
Hi,
See
http://maven.apache.org/plugins/maven-ear-plugin/examples/customize-file-name-mapping.html
for custom filename mapping.
Robert
Op Fri, 07 Feb 2014 15:21:54 +0100 schreef Reto Hablützel
ret...@rethab.ch:
Hi there,
I built an ear using the maven-ear-plugin (version 2.6
of things dragged in with
the latest version of otherwise well-written libraries.
Exclusions need to be added to get what you want in your artifacts.
Ron
On 07/02/2014 9:21 AM, Reto Hablützel wrote:
Hi there,
I built an ear using the maven-ear-plugin (version 2.6).
The ear is configured
-ear-plugin/
examples/customize-file-name-mapping.html for custom filename mapping.
Robert
Op Fri, 07 Feb 2014 15:21:54 +0100 schreef Reto Hablützel
ret...@rethab.ch:
Hi there,
I built an ear using the maven-ear-plugin (version 2.6).
The ear is configured such that it includes two
Robert Scholte wrote:
Hi,
See
http://maven.apache.org/plugins/maven-ear-plugin/examples/customize-file-name-mapping.html
for custom filename mapping.
Hmmm, IIRC the war plugin will automatically prepend the groupId for all
jars with clashing name.
- Jörg
artifacts.
Ron
On 07/02/2014 9:21 AM, Reto Hablützel wrote:
Hi there,
I built an ear using the maven-ear-plugin (version 2.6).
The ear is configured such that it includes two libraries into
the lib
folder, both with the same artifactId as well
The Apache Maven team is pleased to announce the release of the Apache
Maven Ear Plugin, version 2.9
This plugin generates a Java EE Enterprise Archive (EAR) file. It can also
generate the deployment descriptor file (e.g. application.xml).
http://maven.apache.org/plugins/maven-ear-plugin
Wanted to confirm that although you can generate env-entry elements using
the Maven ear plugin, you cannot generate ejb-local-refs in the
application.xml from the plugin itself.
My only alternative is to own the whole application.xml, i.e. disable its
generation, yes?
Thanks,
Best,
Laird
Hello,
I am having difficulties using the packagingIncludes existing in the ear
plugin.
Here is part of my pom file:
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
version2.5/version
the
ejbModule capability (to generate proper application.xml).
I guess, there was something in mind when making m-ear-p to skip those
typeejb/type dependencies when stripping down WAR artifact.
--
View this message in context:
http://maven.40175.n5.nabble.com/Ear-Plugin-skinnyWars-EJB-problem
/type dependencies when stripping down WAR artifact.
--
View this message in context:
http://maven.40175.n5.nabble.com/Ear-Plugin-skinnyWars-EJB-problem-tp563p5723616.html
Sent from the Maven - Users mailing list archive at Nabble.com
Not sure what you mean.
A brief sample config?
--
View this message in context:
http://maven.40175.n5.nabble.com/Ear-Plugin-skinnyWars-EJB-problem-tp563p5723651.html
Sent from the Maven - Users mailing list archive at Nabble.com
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.8
The plugin generates a JavaEE Enterprise Archive (EAR) file.
http://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration:
plugin
configured properly.
I replaced...
groupIdmaven-ear-plugin/groupId
artifactIdmaven-ear-plugin/artifactId
with...
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
Then changed...
includeLibInApplicationXmltrue/includeLibInApplicationXml
Hi,
[This question is also on StackOverflow:
http://stackoverflow.com/questions/12093346/maven-ear-plugin-is-not-including-jarmodule-into-application-xml]
I've been following the example on the maven-ear-plugin site that [shows how to
add third-party libraries to the generated application.xml
I worked it out. I was being an idiot as usual. User error.
Strangely it was producing the EAR file pretty much correctly, even though my
plugin wasn't configured properly.
I replaced...
groupIdmaven-ear-plugin/groupId
artifactIdmaven-ear-plugin/artifactId
Hi Stuart,
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
FWIW you can leave off the groupId if it begins with
org.apache.maven.plugins and Maven will figure out what you mean. Very
handy since the vast majority of the plugins you typically want to
configure
laredotornado-3 wrote:
Hi,
I'm using Maven 3.0.3 and trying to use the maven-ear-plugin (2.7). When
building the ear project, I'm getting the error, [ERROR] Failed to
execute goal
org.apache.maven.plugins:maven-ear-plugin:2.7:generate-application-xml
(default-generate-application-xml
Hi,
I'm using Maven 3.0.3 and trying to use the maven-ear-plugin (2.7). When
building the ear project, I'm getting the error, [ERROR] Failed to execute
goal org.apache.maven.plugins:maven-ear-plugin:2.7:generate-application-xml
(default-generate-application-xml) on project orders-ear:
Artifact
project. - [Help 1]. I'm losing my mind because looking at my pom.xml
file, it IS a dependency of my project. Here is my pom.xml file ...
Don't just look at the pom.xml file. Look at the pom which Maven sees
as generated by mvn help:effective-pom.
For example, I see that you did not declare
I'm looking at this sentence:
Artifact[app-client:org.mainco.myco:myclient] is not a dependency of the
project.
See the app-client? Could it be that the as this is a
appClientModule the plugin is adding a classifier (app-client) or
something?
The order in the a:b:c doesn't follow the de facto
/dependency
/dependencies
build
finalNameapp/finalName
plugins
plugin
artifactIdmaven-ear-plugin/artifactId
version2.7/version
configuration
version5/version
I'm not sure about different behaviors. But I would normally get the JAR and
WAR plugins to edit respected modules' MANIFEST files.
-Original Message-
From: Mauricio
Sent: July-09-12 12:55 PM
Subject: maven-ear-plugin - How to manipulate Manifest.MF of webModule and
ejbModule?
Hello
I need help with the ear plugin.
?xml version=1.0?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
parent
artifactIdILD_Export
/configuration
/plugin/
--
View this message in context:
http://maven.40175.n5.nabble.com/Ear-Plugin-skinnyWars-EJB-problem-tp563p5611958.html
Sent from the Maven - Users mailing list archive
I am trying to create a multi-module skinny war exploded EAR by using the
skinnyWars option of the maven-ear-plugin. The problem I am having is
that the EJB module dependencies of the WAR modules (there are 5) are being
left in the WEB-INF/lib directory of the WAR modules as well as unpacked
I am trying to create a multi-module skinny war exploded EAR by using the
skinnyWars option of the maven-ear-plugin. The problem I am having is
that the EJB module dependencies of the WAR modules (there are 5) are being
left in the WEB-INF/lib directory of the WAR modules as well as unpacked
On Fri, Feb 3, 2012 at 6:44 PM, Daivish Shah daivish.s...@gmail.com wrote:
Do we have any guideline or any link from where i can read which all Jboss
TAG supported by MAVE EAR plugin ?
Thanks.
In the doc (see JBoss support):
http://maven.apache.org/plugins/maven-ear-plugin/usage.html
S
Thanks Stephane
On Sun, Feb 26, 2012 at 7:39 PM, Stephane Nicoll
stephane.nic...@gmail.comwrote:
On Fri, Feb 3, 2012 at 6:44 PM, Daivish Shah daivish.s...@gmail.com
wrote:
Do we have any guideline or any link from where i can read which all
Jboss
TAG supported by MAVE EAR plugin
Hi All,
I found the correct problem.
It wasn't related to DOCTYPE at all.. Wayne was correct.
I have to apply this tag in MAVEN EAR plugin, The exception was coming when
i try to look for WSDL for the webservice. It was throwing exception
because classloader was unable to find the webservice
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
configuration
defaultLibBundleDir/APP-INF/lib/defaultLibBundleDir
version5/version
modules
ejbModule
groupIdtest-project/groupId
artifactIdtest-ejb/artifactId
bundleFileNametest-ejb-0.0.1
I created one webservice and i am applying version5/version and we
are using Jboss 5.1.2EA version.
And it's not able to generate WSDL if i apply DOCTYPE tag over there.
If i remove that tag from jboss-app.xml it's working all right...
Talk to the JBoss folks about that. Sounds like a bug on
this. Apply
your own jboss-app.xml under this folder structure and remove
jboss/jboss tag from MAVEN EAR plugin and it will take your local
version whenever you hit the mvn install command.
|-- pom.xml
`-- src
`-- main
`-- application
`-- META-INF
`-- jboss
TO ME it looks like MAVEN EAR PLUGIN team needs to work with Jboss TEAM and
have to make this correction in MAVEN EAR PLUGIN.
You're talking about getting changes that you need for your personal
work into an open source project.
If a company wants something badly enough, they will pay one
as it's really
healthy discussion and thoughts i get from MAVEN USERS group.
Thanks again.
On Thu, Feb 2, 2012 at 12:37 PM, Wayne Fay wayne...@gmail.com wrote:
TO ME it looks like MAVEN EAR PLUGIN team needs to work with Jboss TEAM
and
have to make this correction in MAVEN EAR PLUGIN
On 03/02/2012, at 4:42 AM, Daivish Shah wrote:
Hi Wayne,
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'TestEjbHandlerImpl': Invocation of init
method failed; nested exception is java.lang.LinkageError: loader
constraint violation: loader (instance
:
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.7
The most noteworthy in this release is the support for skinny WAR files.
It is one of the most voted on issues in our JIRA with 50 votes. We
would love to hear your feedback on this new feature
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.7
The most noteworthy in this release is the support for skinny WAR files.
It is one of the most voted on issues in our JIRA with 50 votes. We
would love to hear your feedback on this new feature.
The plugin
, mixed mode, sharing)
maven-ear-plugin version 2.6
Kind regards
Karl Heinz Marbaise
-
Kind regards
Karl Heinz Marbaise
http://www.soebes.de
http://www.skmwiki.de
http://supose.org/wiki/supose
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-ear-plugin-ear-file-can
]
ZIPINFOOPT: [none]
Does someone observed such a behaviour?
Maven 3.0.3 (Windows Plattform)
java version 1.6.0_25
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) Client VM (build 20.0-b11, mixed mode, sharing)
maven-ear-plugin version 2.6
Kind regards
Karl Heinz
with package
So how can i handle this by using EAR plugin ? Or i need to use MAVEN ANT
Plugin and create EAR file by using that ?
Please guide me.
thanks,
daivish.
On Tue, Aug 23, 2011 at 8:50 PM, Wayne Fay wayne...@gmail.com wrote:
So basically i have some CLASS files on my machine/ Which
I am using EJB 2.0 and weblogic workshop 8.1 version. And my EAR has
structure something like below.
So how can i handle this by using EAR plugin ? Or i need to use MAVEN ANT
Plugin and create EAR file by using that ?
I don't use Weblogic Workshop and I have no tool-specific advice to
offer
Hi,
I am using maven-ear-plugin. I want to add following ANT Script files in
MAVEN EAR plugin. How can i do it ?
So basically i have some CLASS files on my machine/ Which are located
..\workshop\output\ and .workshop/WebService/**.
Also i want to add whatever under this directory to EAR
So basically i have some CLASS files on my machine/ Which are located
..\workshop\output\ and .workshop/WebService/**.
Also i want to add whatever under this directory to EAR
\WPSWebService\WEB-INF\
How can i do it using MAVEN-EAR-PLUGIN ?
I don't believe that it is legal to package un
The Maven documentation
sayshttp://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
:
Each of the scopes (except for import) affects transitive dependencies in
different ways, as is demonstrated in the table below. If a dependency is
set to the
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.6
This version brings mainly detection of application client archive
managed by the recent maven-arc-plugin [1]
http://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's
I am having trouble using the ear plugin [version 2.5] with Maven
3.0.3, to create an EAR file for a simple stateless ejb.
I've tried the javaee 6 archetype from mojo - that seems to be just
for the ear module of a multi-module application - accordingly, I've
tried both single and multi module
Try to rename dependancies to dependencies.
—
Yegor Bugayenko
On Tue, Mar 15, 2011 at 3:56 PM, Dave Levitt dave.lev...@gmail.com wrote:
I am having trouble using the ear plugin [version 2.5] with Maven
3.0.3, to create an EAR file for a simple stateless ejb.
I've tried the javaee 6
Levitt dave.lev...@gmail.com wrote:
I am having trouble using the ear plugin [version 2.5] with Maven
3.0.3, to create an EAR file for a simple stateless ejb.
I've tried the javaee 6 archetype from mojo - that seems to be just
for the ear module of a multi-module application - accordingly, I've
You didn't specify the packaging type for the artifact.
packagingear/packaging
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
From:
Dave Levitt dave.lev...@gmail.com
To:
Maven Users List users@maven.apache.org
Date:
03/15/2011 10:56 AM
Subject:
maven ear plugin - simple example
I am
source files]?
That would be the simplest case, and would be a good fit for an
archetype. [may require a new release of the ear plugin]
On Tue, Mar 15, 2011 at 11:17 AM, Timothy Mcginnis
tmcgi...@aessuccess.org wrote:
You didn't specify the packaging type for the artifact.
packagingear/packaging
Hi,
the error come and go randomly. I use the maven-ear-plugin 2.5-SNAPSHOT to
generate application-name, see http://jira.codehaus.org/browse/MEAR-128. I'm
using it in a JEE 6 project where I want to access the global JNDI tree. It
would be great if you could create a release soon, the sooner
maven-ear-plugin 2.5 was released yesterday.
/Anders
On Sat, Jan 29, 2011 at 15:00, viggo.navarsete viggo.navars...@gmail.comwrote:
Hi,
the error come and go randomly. I use the maven-ear-plugin 2.5-SNAPSHOT to
generate application-name, see http://jira.codehaus.org/browse/MEAR-128.
I'm
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.5
This new release brings additional compatibility with Java EE 6,
automatic id generation for modules and a few bug fixes.
http://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version
12, 2011 at 11:12 AM, Viggo Navarsete viggo.navars...@gmail.com
wrote:
Hi,
I'm using maven-ear-plugin 2.5-SNAPSHOT, and for the past week or so, we've
had problems downloading it from Maven, output is this:
Downloading:
http://mavenrepo.pd.tracetracker.com:9998/repo/org/apache/maven/plugins
Hi,
I'm using maven-ear-plugin 2.5-SNAPSHOT, and for the past week or so, we've
had problems downloading it from Maven, output is this:
Downloading:
http://mavenrepo.pd.tracetracker.com:9998/repo/org/apache/maven/plugins/maven-ear-plugin/2.5-SNAPSHOT/maven-ear-plugin-2.5-20110111.075142-136.pom
Size: 10664
Please respond to
Maven Users List users@maven.apache.org
To
Maven Users List users@maven.apache.org
cc
Subject
Re: Ear plugin issue
Entity
HSBC Bank plc - HBEU
What error message do you get exactly? ClientModules is not a dependency
of
the project or something
Hi All,
I am trying to get the ear plugin working.
Followed all the guidelines but could not get it working as its not able
to find the module that I want to package within the ear
It looks for the module in my nexus repository but does not find it.
I have also got the Resolve workspace
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
version2.4.2/version
configuration
modules
jarModule
groupIdroot.ProjectX/groupId
artifactIdClientModules/artifactId
/jarModule
/modules
users@maven.apache.org
Cc:
users@maven.apache.org
Date:
08/26/2010 10:21 AM
Subject:
Re: Ear plugin issue
It seems the attachments are not allowed. I have included the ear pom
below
groupIdroot.ProjectX/groupId
artifactIdEarAssembler/artifactId
version1.0/version
nameEarAssembler/name
packagingear/packaging
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
version2.4.2/version
configuration
Just that unable to find clientModule
Stephane Nicoll stephane.nic...@gmail.com
Aug 26 2010 18:35
Mail Size: 10664
Please respond to
Maven Users List users@maven.apache.org
To
Maven Users List users@maven.apache.org
cc
Subject
Re: Ear plugin issue
Entity
HSBC Bank plc - HBEU
With -X -e, is it any clearer as to what it's looking for? What the GAV is?
-Original Message-
From: nishant@hsbcib.com [mailto:nishant@hsbcib.com]
Sent: Thursday, August 26, 2010 1:37 PM
To: Maven Users List
Cc: Maven Users List
Subject: Re: Ear plugin issue
Just that unable
The Maven team is pleased to announce the release of the Maven Ear
Plugin, version 2.4.2
This version fixed possible corruption/incorrect data issues that can
occur on non-windows machines
due to threading issues. It also adds @threadSafe support for maven3.
http://maven.apache.org/plugins/maven
in my build though.
Thanks.
C.
Wale12 wrote:
I go into the maven repository to
\org\apache\maven\plugins\maven-ear-plugin and delete the 2.4.1. folder
then run the build again.
snicoll wrote:
And it probably doesn't. I am not sure I get your it works if I delete
I changed the
earSourceDirectory./earSourceDirectory
to
earSourceDirectory${basedir}/earSourceDirectory
No difference in my build though.
Thanks.
C.
Wale12 wrote:
I go into the maven repository to
\org\apache\maven\plugins\maven-ear-plugin and delete the 2.4.1. folder
then run
I go into the maven repository to \org\apache\maven\plugins\maven-ear-plugin
and delete the 2.4.1. folder then run the build again.
snicoll wrote:
And it probably doesn't. I am not sure I get your it works if I delete
the
plugin thing. Can you replace the . by ${basedir} to avoid any
I have a weird issue with a project I have. I am using maven 2 and version
2.4.1 of the ear plugin and am using the version 5 no application.xml
options for packing the ear.
plugin
artifactIdmaven-ear-plugin/artifactId
version2.4.1/version
configuration
version5/version
maven 2 and version
2.4.1 of the ear plugin and am using the version 5 no application.xml
options for packing the ear.
plugin
artifactIdmaven-ear-plugin/artifactId
version2.4.1/version
configuration
version5/version
generateApplicationXmlfalse/generateApplicationXml
of the ear plugin and am using the version 5 no application.xml
options for packing the ear.
plugin
artifactIdmaven-ear-plugin/artifactId
version2.4.1/version
configuration
version5/version
generateApplicationXmlfalse/generateApplicationXml
earSourceDirectory
1 - 100 of 402 matches
Mail list logo
