Vincent Massol wrote:
>
>
>>-----Original Message-----
>>From: James CE Johnson [mailto:[EMAIL PROTECTED]]
>>Sent: 25 August 2002 12:33
>>To: [EMAIL PROTECTED]
>>Subject: Re: [War plugin] Latest changes
>>
>>Hi Vincent,
>>
>>
>>
>>>James,
>>>
>>>Simply run "maven war:webapp". This will create an expanded webapp
>>>
>>>
>in
>
>
>>>target/, which you can then copy wherever you want in a post goal in
>>>your maven.xml.
>>>
>>>
>>Yea, we're doing that. The other thing we're doing is creating
>>a JBoss-deployable warfile (exploded warfile actually) of the maven-
>>generated project site. The xdocs, checkstyle, etc... To do that we
>>build a WEB-INF in ${webapp.test.dir}/${maven.id}-site.war/ and
>>add a few things to it before copying over ${maven.docs.dest}.
>>I'm
>>just wondering if there's a better/cleaner way of doing such.
>>
>>
>>
>
>Ok, this is different from the WAR plugin. This is about deploying the
>generated docs in a given format.
>
Yes, absolutely. But we're using some of the same approaches/layout
stuff that you're using in the war plugin and I want to stay consistent
with your way of doing things.
>The best is simply to have a post Goal
>for the "site" target (or even better, another target called something
>like "site:install-war" or similar) that simply uses the Ant <war> task
>
><war warfile="/destination/location/xxx.war">
>[...]
></war>
>
>But it falls out of the War plugin which has a different goal: generate
>war of sources.
>
Right. Of course.
>>This just ocurred to me too... Does ${maven.conf.dir} go away
>>now that you're expecting the web.xml in
>>${maven.src.dir}/webapp/WEB-INF/web.xml?
>>
>>
>>
>
>The war plugin does not use maven.conf.dir anymore but maven.conf.dir
>does not go away. It is used by other plugins and is not owned by the
>war plugin (the naming convention for all properties owned by the war
>plugin is : maven.war.*).
>
Ok. Thanks.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
