I could achieve this by configuring the ear plugin like this:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<configuration>
<unpackTypes>war</unpackTypes>
<workDirectory>E:\Programs\JBoss510\server\default\deploy\ejb3Test2.ear</workDirectory>
</configuration>
</plugin>
</plugins>
</build>
brianwainwright wrote:
>
> Hi,
>
> I am currently trying to move my teams large
> multi-project/multi-webapp/multi-ear application from Maven 1.x to Maven
> 2, and overcome most of the problems I've had on the way, but there's one
> issue I can't work out.
>
> Our current (Maven 1.x) build, we have a customized goal which produces an
> exploded ear which in turn contains an exploded war - (our current
> practise is for developers to deploy fully exploded ears/wars on their own
> JBoss servers while developing.). We do this by "unwar"ing any bundled
> war dependencies in the exploded ear.
>
> Is there any (simple) way to produce the same kind of fully exploded ear
> in M2?
>
> I've looked at war:exploded, which will build the exploded war, but then
> the ear plugin will look for the .war artifact in the repository when
> trying to bundle it's dependencies, so the exploded war wouldn't be used
> when packaging the ear?
>
> I've also looked at the maven-explosion plugin, which could possibly work
> for us, but it seems inefficient to war/ear the original artifacts and
> then unpack them to explode them when their exploded directories already
> exist.
>
> Thanks for your help,
>
> Brian Wainwright
> Developer
> Burns E-Commerce
> Mansion House, Manchester Road, Altrincham, Cheshire, WA14 4RJ, UK
> http://www.burnsecs.com
> mailto:[email protected]
>
>
>
--
View this message in context:
http://www.nabble.com/Exploded-WAR-in-exploded-EAR-tp3968873p24501387.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
