Jean-Fran�ois,
I did this with a custom goal, something like this:
<goal name="myEar">
<attainGoal name="war"/>
<copy todir="target/ear" overwrite="yes">
<fileset dir="src/application" />
<fileset dir="target" includes="*.war" />
</copy>
<attainGoal name="ear"/>
</goal>
And
maven.ear.src=target/ear
Hope this help
----------------------------------------------------------------------
------
Edgar Gonz�lez Gonz�lez
VALHALLA Project, s.a.
Chief Technology Officer
Web: www.valhallaproject.com
E-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
Phone: +58-212-242.4379 / 6662 / 4055 / 6475
Fax: +58-212-242.6809
"The limits of my language mean the limits of my world."
Ludwig Wittgenstein
----------------------------------------------------------------------
------
Jean-Fran�ois El Fouly <[EMAIL PROTECTED]> wrote:
(05/07/2004 06:35)
>Suppose I have a project with a web application. At the moment, I build the
>war in this project and the ear in another project that basically has just
>a POM, a maven.xml and build.properties.
>Though it seems that the ear plugin was designed to build in the web
>application project itself rather than in another project (since it copies
>the built EAR in application/ears/application-version.ear.
>
>On the other hand, if I want to build the EAR in the same project, I need
>to include the application war as a dependency, so I have some kind of
>chicken-and-egg problem (BTW it became even more difficult since wars now
>have versions).
>
>Did I miss any obvious recipe ?
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
