Eric,
where do the .vm files go?
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
| "Eric Pugh" <[EMAIL PROTECTED]>
05/01/02 09:59 PM
|
To: <[EMAIL PROTECTED]> cc: Subject: RE: [PROPSAL] WAR build process (start of build-j2ee.xml) |
I would love to see a war build target... I am currently building some
war's, but mostly patching in and around maven, not actually leveraging it!
Let me know what you need tested!
Where do you see jsp files etc living? I currently have them all just
jumbled up in /src/web/. In there as well are .vm Velocity files, and .css
and image files as well.
Eric
-----Original Message-----
From: Christian Willy Asmussen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 30, 2002 11:58 PM
To: Maven Dev List
Subject: Re: [PROPSAL] WAR build process (start of build-j2ee.xml)
Maybe, if the logic for the maven.war.xxxBuildFile and
maven.war.xxxBuildTarget is implemented abstractly, it could become
maven.yyy.xxxBuildFile and maven.yyy.xxxBuildTarget and with yyy beeing
maven targets (doc,site,etc) solving my previously posted question about
calling project targets from maven:* targets.
One thing that seems very important to me is to "forward" some kind of
reference to the project classpath build from the set of <depencency> jars
to the target called. This would avoid having to set the classpath by hand
on several diferent files.
On Tue, Apr 30, 2002 at 11:37:08PM -0400, Glenn A. McAllister wrote:
> Goals
> =====
>
> This process is designed to build one war, with little or no modification
> to the POM.
>
> Directory Layout
> ================
>
> WAR Repository
> --- ----------
> Static content src/webapps/${maven.war.name}
> WEB-INF/web.xml src/conf/${maven.war.name}-web.xml
> WEB-INF/classes ${build.dir}/**/*.class
> WEB-INF/lib Dependent jars from POM (dependencies.set)
>
> Properties
> ==========
>
> Name Description
> ---- -----------
> maven.war.name The name of the WAR file. This must be set -
> there is no default value.
>
> maven.war.content Static content location, defaulting to
> src/webapps/${maven.war.name}.
>
> maven.war.classes The WEB-INF/classes files, defaults to
> ${build.dir}/**/*.class
>
> maven.war.lib The WEB-INF/lib fileset, defaults to the set
> of jars from the <dependency> elements.
> (dIon - how was this to work again?)
>
> maven.war.manifest The manifest file, defaulting to the standard
> Maven manifest.
>
> maven.war.prepareBuildFile These two properties are used to provide a
> maven.war.prepareBuildTarget hook for doing any additional preparation;
> see the "Process" section below.
>
> maven.war.updateBuildFile These two properties are used to provide a
> maven.war.updateBuildTarget hook for doing any additiona work on the
> generated WAR file; see the "Process" section
> below.
>
> Build File
> ==========
>
> The build filename will be build-j2ee.xml and the target to create the war
> is (surprise) war. The delegator target name is maven:war. The
> build-j2ee.xml file has all the standard init targets.
>
> Process
> =======
>
> 1. Delegate to compile and jar-resources in build-maven.xml to create the
> *.class files and move any resource files into place.
>
> 2. If the properties ${maven.war.prepareBuildFile} and
> ${maven.war.prepareBuildTarget} are set, execute
>
> <ant antfile="${maven.war.prepareBuildFile}"
> target="${maven.war.prepareBuildTarget}" />
>
> This provides a hook to do any additional prep work (like moving
> template files in the classes directory, etc.) before creating the war.
> Thanks to Jason for the technique.
>
> 3. Create the WAR file : target/${maven.war.name}.war
>
> 4. If the properties ${maven.war.updateBuildFile} and
> ${maven.war.updateBuildTarget} are set, execute
>
> <ant antfile="${maven.war.updateBuildFile}"
> target="${maven.war.updateBuildTarget}" />
>
> This provides a hook to do any post processing required on the war
> file.
>
> Afterwards
> ==========
>
> You know, I think it would have been faster to simply write the build file
> than this email. :)
>
> Note that while the goal of this process is to build a single war file,
> it can already build mutliple wars with differing web.xml and static
> content with the same set of WEB-INF/classes and WEB-INF/lib files due to
> the use of the ${maven.war.name} property. Its a start.
>
> Glenn McAllister
> SOMA Networks, Inc.
>
>
>
>
>
>
>
>
>
>
--
There is no limit to what you can do
if you don't care who gets the credit.
- Keynote
