This is build no.4.
It uses maven, and it does so in a maven-like fashion (in contrast to [build no.5]). It replaces all maven and ant build scripts currently in the magnolia svn repository.

My setup works as follows:

• I have one project containing the latest Magnolia source code from the svn repository ("project 1")
• Another project holds an author instance ("project 2"). Here I'm doing my webapp and template development.

"Project 2" was originally set up using Magnolia 2.

How this works

In order to test my changes with the latest and greatest 2.01 source code of Magnolia, do the following:

1. Go to "project 1" and update it using SVN so that it contains the latest changes and patches.
2. Run the Maven goal create-snapshot by calling "maven create-snapshot" in the project root directory. This target generates snapshots in Maven subprojects, which contain the compiled code, the source code, and additional webapp elements consisting of GIFs, JSPs, etc. and configuration files.
3. Call maven install-snapshot. This installs the snapshots created in the previous step in the local maven repository.

This concludes building and locally deploying Magnolia.

My "project 2" Maven project.xml file can now use dependencies in order to refer to these snapshots. I will - at a later point in time - publish a sample maven POM for "project 2".

Here is a list of the artifact and group ids:

The build uses the install-snapshot goal of the artifact plug-in and thus also installs timestamped versions of the snapshots you can refer to.

Installation

In order to install this, do the following:

1. Check out the latest Magnolia code from the SVN repository.
2. Remove the following files: build.xml, project.xml, project.properties
3. Unzip the content of the attached zip file into the project root directory.
   Please send all feedback to the Magnolia developer list (as indicated in the magnolia POM ).
   
   

Other known authors include :

• AndreasWeder
• OrtwinGlueck