On Wed, Apr 03, 2002 at 12:57:13PM -0800, Chris Kimpton wrote:
> As I understand maven, we will need a jetspeed project.xml and
> build-maven.xml.

Actually, you don't need a build-maven.xml if you just add the Maven
delegators (http://jakarta.apache.org/turbine/maven/build-file.html)
directly to your existing build file.  However, if you want to slowly
introduce the Maven build system to your users, then you can follow the
approach that the Turbine projects have taken, which is to create a
build-maven.xml file with Maven delegators in there (just copy the
build-maven.xml from Stratum for example).

> It will be able to do the update-jars, compile and jar out of the box
> (with the correct project.xml).

Yes.

> For jetspeed we need to build a .war file and also an expanded
> version of it.
> 
> So - do we add a custom task for this to the build-maven.xml ?  Or
> amend the standard build-maven.xml in {maven.home} ?

It is not a good idea to modify ${maven.home}/build-maven.xml as this
file will be replaced the upon subsequent Maven installs.  It is not the
correct place to add customizations.  Depending on the approach you take
(described above), you can either: 

   - just use your existing 'war' target in your build file if you
     integrate the Maven delegators directly in there, or
 
   - you can call your existing 'war' target from your project's
     build-maven.xml, or 

   - you can add a new 'war' target in your project's build-maven.xml.  

There is nothing special about a project's build-maven.xml file other
than the fact that its happens to hold a block of Maven delegators.  Do
as you wish to it.  

I've started an Integration document that covers some of this
information, you can find it here:

http://jakarta.apache.org/turbine/maven/integrate.html

Or just click on the "Getting Started" link on the Maven homepage for a
slew of information.

Finally, there are now Maven mailing lists that should be used for this
discussion.  Please see the "Mailing List" link on the Maven homepage
for more information.

Thanks,
Pete


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to