> > I got the war task working :)
> >
> > Steps:
> >
> > Copy:
> >
> > <property name="maven.war.classes" value="${maven.build.dest}"/>
> > <property name="maven.war.file" value="${maven.build.dir}/${maven.
> > war.name}.war"/>
> Didn't need this one?
I was using maven war:build-war to get it working. It complained about not
having the name of the war file, due to the fact the second property was
not being executed. It was in a goal named 'war'. I don't know if this is
a constructor of some kind, but none of the three war goals listed in
maven -g seemed to execute the war goal. war:build-war, war:build-webapp
and war:webapp. I expected to see a war:war in maven to fire off the war
goal in the plugin.jelly, but no dice. I could go and learn jelly, but
that's getting quite a high level of time usage for an attempt to build a
war. Gotta do outside work time.
I don't pretend to think this is the right way, but it's what comes from
reading the source.
Looking at the CVS HEAD, I see that the war plugin's plugin.jelly seems to
have changed a fair chunk. Should I be running the risk of nightly builds
to get war functionality?
> > from the war goal to the war:build-war goal in:
> >
> > $MAVEN_HOME/plugins/maven-war-plugin-1.1-SNAPSHOT/plugin.jelly
> >
> > Added:
> >
> > maven.war.webxml=deploy-xml/web.xml
> If the web.xml is in src/webapp/WEB-INF, then this step is unnecessary,
> right?
Right. I'm trying to avoid having to restructure the entire project to
suit Maven.
>
> > maven.war.name=genscape
> This is only to change the war name generated from the default (which is
> id-version.war), right?
See above :) We can't go changing the war name as this changes already
published urls.
> > made a src/webapps/genscape/
> The war plugin currently uses src/webapp/ .... ?
Seems to use webapps. If I don't give it a webapps directory, it
complains.
>
> > directory and copied my html/flash stuff in there.
> >
> > And I have a big war.
>
> Cool.
> > Oh, and added:
> >
> > <properties>
> > <war.bundle.jar>true</war.bundle.jar>
> > </properties>
A bit early though. Currently we're not seeing the dependent jars going
into the WEB-INF/lib directory. Tried on Windows and Linux.
Looking at the cvs log for plugin.jelly seems to suggest it should be:
<metaEntries>
<metaEntry>war.bundle.jar:true</metaEntry>
</metaEntries>
Hen
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
