EAR plugin: problem with unpacking modules

Hi! Maven EAR plugin is unpacking modules content right into the working folder :-( Maven version 2.0.8 (tried on 2.0.6 and 2.0.7 with the same result) Here's the POM: project parent artifactIdmystuff/artifactId groupIdmystuff/groupId version1.0/version /parent

Re: EAR plugin: problem with unpacking modules

Problem was successfully solved by executing the 'clean' goal before packaging. 2008/2/14, Pavel Kaplin [EMAIL PROTECTED]: Hi! Maven EAR plugin is unpacking modules content right into the working folder :-( Maven version 2.0.8 (tried on 2.0.6 and 2.0.7 with the same result) Here's the

EAR plugin problem

I have a problem with configuring the EAR plugin so it copies the depended jar files to by APP-INF/lib directory in the EAR file; the plugin places the jar files in the root directory, which makes my deployment fail. See the configuration of the EAR file below. Can anyone point me to a fix?

Re: EAR plugin problem

Try defaultJavaBundleDirAPP-INF/lib/defaultJavaBundleDir instead. I believe the BBwMaven book is inaccurate at this point. -aps On 12/4/06, Lars Rosenberg Nielsen [EMAIL PROTECTED] wrote: I have a problem with configuring the EAR plugin so it copies the depended jar files to by APP-INF/lib

[m2] Ear Plugin problem... Generating EAR from two WARs (subprojects)

Having a problem understanding the directory structure for the master project which contains multiple subprojects. I am trying to create an ear from two wars which are generated from two subprojects. earbuilderproj - pom.xml (I want this to generate an EAR) - proj1 -

Re: [m2] Ear Plugin problem... Generating EAR from two WARs (subprojects)

On Thu, 1 Sep 2005 [EMAIL PROTECTED] wrote: Hi, In your root project (earbuilder) you need to specify: - two dependencies on the two war projects, with typewar/type - specify packagingear/packaging - use m2 install. That way the lifecycle assosiated with packaging ear kicks in and your

Re: [m2] Ear Plugin problem... Generating EAR from two WARs(subprojects)

Re: [m2] Ear Plugin problem... Generating EAR from two WARs(subprojects) In your root project (earbuilder) you need to specify: - two dependencies on the two war projects, with typewar/type - specify packagingear/packaging - use m2 install. That way the lifecycle assosiated with packaging

Re: [m2] Ear Plugin problem... Generating EAR from two WARs(subprojects)

I had a copy/paste error in the last email... here is the pom.xml file that i am using... I'm still having the issues as described in the previous email. project modelVersion4.0.0/modelVersion groupIdcom.myco.apps/groupId artifactIdearbuilderproj/artifactId packagingear/packaging

Re: [m2] Ear Plugin problem... Generating EAR from two WARs (subprojects)

Eric, there is a property that you have to set in your build.properties in order for maven to create the application.xml file for you. http://maven.apache.org/reference/plugins/ear/properties.html maven.ear.appxml.generate = true Manuel At 08:41 AM 9/1/2005, you wrote: Having a problem

Re: [m2] Ear Plugin problem... Generating EAR from two WARs(subprojects)

Hi eric, The way I solved this is by creating a pom porject that includes all three modules and make ear to contain only the dependency. I.e. [apps] |-module--[earBuilderProj] | | | | depend depend |