James CE Johnson <[EMAIL PROTECTED]> wrote on 26/08/2002 01:27:36 AM:
> [EMAIL PROTECTED] wrote:
> Moving [webapp]-war.xml out of ${maven.conf.dir} will cause us to make a
> few minor changes but nothing drastic. I'll probably end up creating a
> src/site/... to keep the site's jboss-web.xml and web.xml files and
whatnot.
>
> I was just wondering if someone else might already be doing this kind of
> thing and we could use it instead of using our home-grown solution.
Not yet, but I like the idea to capture the project state in a single file
(WAR) that can be archived somewhere.
A few questions on the goal you're using:
| <copy file="${maven.conf.dir}/site-web.xml"
| tofile="${webapp.test.dir}/${maven.id}-site.war/WEB-INF/web.xml"/>
Is web.xml necessary?
| <copy file="${maven.conf.dir}/site-jboss-web.xml"
| tofile="${webapp.test.dir}/${maven.id}-site.war/WEB-INF/jboss-web.xml"/>
JBoss's customised web.xml, right - what's in it?
| <copy file="${maven.conf.dir}/tests-config.xml"
|
tofile="${webapp.test.dir}/${maven.id}-site.war/WEB-INF/classes/config.xml"/>
What do you use this one for?
| <copy
todir="${webapp.test.dir}/${maven.id}-site.war/WEB-INF/classes">
| <fileset dir="${maven.conf.dir}"
|includes="users.properties,roles.properties"/>
Ditto..?
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
