Goal

The goal is to develop a strategy to migrate all existing Glast projects from Maven1 to Maven2 is as unobtrusive a way as possible. The reasons to switch to maven2 are

Support for maven1 is fading away
Netbeans6, due to be released before end-of-year, has support for maven2 built-in (but not maven1)
Maven2 has many improvements, including simpler dependency management

We will not be able to move all projects over-night, so we need a strategy for which order to move projects, and how projects which have moved can continue to co-exist with projects which have not moved. We will need to provide clear instructions to developers to allow them to move their projects.

We should start with some simple projects, like org-glast-groupmanager.

Requirements

We need to maintain the features we have in maven1, including
- Ability to check projects out and build them in Netbeans
- Ability to deploy projects using the built-in netbeans tomcat server (Netbeans deploy)
- Ability to use in-place deploy so that JSP pages can be edited and the effects seen immediately without the need to redeploy
- Ability to deploy projects from netbeans to the development (tomcat03) and production (tomcat*) tomcat servers.
Ability for cruise-control to build projects. This should not be too hard since cruise-control has support for maven2
Ability to deploy snapshots and releases to a central Glast maven2 repository
Ability to deploy sites to http://glast-ground.slac.stanford.edu/docs

Possible additional features

Right now there is a lot of boiler-plate code which has to be copied into each new Glast project. For freehep Mark set things up so their was a master project which other projects inherited from so that we didn't have to repeat the same information in each sub-project. A maven "archetype" for Glast projects might also be a good way to achieve this.
Now that we have 12 tomcat servers it is difficult to remember which server each application should be deploy to. It would be nice to be able to do something like mvn -Dmode=prod tomcat:deploy and have the application automatically deploy to the correct location. This would require some type of custom maven plugin which would talk to the glastgen database.

For Developers

Developing Projects

Parent Repository

All projects have to specify in the pom file the repositories where to find the parent. So the following code is required in every project:

    <repositories>
        <repository>
            <id>glast-maven2</id>
            <name>GLAST Maven 2 central repository</name>
            <url>http://glast-ground.slac.stanford.edu/maven2</url>
        </repository>
        <repository>
            <id>glast-maven2-snapshots</id>
            <name>GLAST Maven2 central SNAPSHOTS repository</name>
            <url>http://glast-ground.slac.stanford.edu/maven2/SNAPSHOTS</url>
        </repository>
    </repositories>

JAR

Parent

A jar project should inherit from org-glast-maven-jar-project; so in your pom add:

    <parent>
        <groupId>glast</groupId>
        <artifactId>org-glast-maven-jar-project</artifactId>
        <version>1.2</version>
    </parent>

WAR

Parent

A jar project should inherit from org-glast-maven-war-project; so in your pom add:

    <parent>
        <groupId>glast</groupId>
        <artifactId>org-glast-maven-war-project</artifactId>
        <version>1.2</version>
    </parent>

Final Name

The final name of the war file is to be set in the pom file as:

    <build>
        <finalName>ServerMapping</finalName>
    </build>

This name is the name of the produced war file and it must be identical to the Application's context. It is also used by the Maven Tomcat Deploy plugin to find the production deployment server.

Source Location

Maven2 expects the source files to be located in src/main/webapp. Some of our projects have the source code in src/webapp. To tell maven2 to look in the latter location add the following to your pom file:

    <build>
        <plugins>
            <plugin>
                <artifactId>maven-war-plugin</artifactId>
                <configuration>
                    <warSourceDirectory>${basedir}/src/webapp</warSourceDirectory>
                </configuration>
            </plugin>
        </plugins>
    </build>

SCM Plugin

CVS repositories cannot be inherited by the parent pom, so each project will have to add the following lines to their pom file:

    <scm>
        <connection>scm:cvs:pserver:anoncvs@glast-java.slac.stanford.edu:/cvs/java:${artifactId}</connection>
        <developerConnection>scm:cvs:ext:@glast-java.slac.stanford.edu:/cvs/java:${artifactId}</developerConnection>
        <url>http://www-glast.stanford.edu/cgi-bin/viewcvs/${artifactId}/?root=java</url>
    </scm>

Tomcat manager authentification

To be able to deploy to a tomcat server it is necessary to provide the manager's username and password. This can be done in a file called settings.xml located in your HOME\.m2 directory.

For GLAST you have to add the glastServer server element as shown below:

<?xml version="1.0" encoding="UTF-8"?>
<settings>
   <servers>
     <server>
       <id>glastServer</id>
       <username>glast</username>
       <password>GammaRay</password>
     </server>
   </servers>
</settings>

List of Modules in javacvs

Module Name	Converted	In Hudson	Comments
org-glast-maven-project
org-glast-maven-jar-project
org-glast-maven-jar-archetype
org-glast-maven-war-project
org-glast-maven-war-archetype
org-glast-maven-aida-project
org-glast-tomcat-deploy-maven-plugin
org-glast-base-web
org-glast-base-application
org-glast-servermapping
org-glast-groupmanager			Unnecessary dependence on aidatld. Still on branch
org-glast-dataportal-astro-model
org-glast-datahandling-common
org-glast-telemetry-trending
org-glast-telemetry-trending-web
org-glast-installer-gui
org-glast-releasemanager
TomcatConfigurationBuilder
org-glast-dataportal-astro
org-glast-isoc-cfgwebbrowser
org-glast-reports-web
org-glast-isoc-common
org-glast-resources
oracle
org-glast-dataportal-history
org-glast-isoc-logging
org-glast-runquality-web
org-glast-historyprocessing-web
org-glast-latba-web
org-glast-dataportal-model			Version 1.8 but depends on SNAPSHOTs
org-glast-isoc-mpwebview
org-glast-dataportal-portal
org-glast-jobcontrol			Version 1.8
org-glast-servermon-web
org-glast-asp-skimmer
org-glast-dataportal-simpleskimmer			Unnecessary dependence on aidatld
org-glast-latcatalog-web
org-glast-shiftschedule-web
org-glast-dataportal-skimmer-fits
org-glast-logging
org-glast-aspdataviewer-web
org-glast-dataportal-wired
org-glast-maven-jar-archetype
org-glast-skimmer-web
org-glast-dataportal-xroot-gateway
org-glast-sourcemonitoring
org-glast-dataprocessing-web
org-glast-maven-plugin-parent
org-glast-sourcemonitoring-web
org-glast-dataqualitymonitoring
org-glast-systemtests-web
org-glast-calibrationtrending
org-glast-dataqualitymonitoring-web
org-glast-telemetry-apidstats
org-glast-calibrationtrending-web
org-glast-dataserver-portal
org-glast-maven-web-project
org-glast-telemetry-monitor-web
org-glast-cas-client-example
org-glast-dataserver-web
org-glast-maven-xmlbeans-plugin
org-glast-telemetry-rtdisplay-web
org-glast-cas-server
org-glast-downloadmanager
org-glast-mc-requests
org-glast-clock
org-glast-elog-base
org-glast-monitor
org-glast-common
org-glast-elog-web
org-glast-pipeline-client
org-glast-telemetry-trends
org-glast-commons-web
org-glast-fastmonitoring
org-glast-tld-timeline
org-glast-confluence
org-glast-fastmonitoring-web
org-glast-countdown-clock
org-glast-fcmonitor
org-glast-pipeline-server
org-glast-datacat-client			Version is 2.3.2 but depends on SNAPSHOTs. Test do not work
org-glast-fcwebview
org-glast-pipeline-web
org-glast-util-grep
org-glast-datacat-server
org-glast-visitor-web
org-glast-datacat-sp			Version is 2.2.1, but depends on SNAPSHOTs
org-glast-glossary
org-glast-web-base-application
org-glast-datacatalog-web
org-silicondetecor-web
org-glast-dataflow-web
org-glast-groupmanager-example
tomcat
org-glast-fcwebview-portlet			What do we do with portlet code?
org-glast-portlet			What do we do with portlet code?
org-glast-portlet-base			What do we do with portlet code?
org.glast.portlet			What do we do with portlet code?
org-glast-portlets			What do we do with portlet code?
org-glast-skeleton-portlet			What do we do with portlet code?
org-glast-portal-theme			What do we do with portlet code?
org-glast-grbmonitoring-web			Is this obsolete?
org-glast-asdc-sourceviewer			Is this obsolete?
org-glast-asp-sourceviewer			Is this obsolete?
org-glast			Obsolete
org.glast.test			Obsolete
org-glast-hello			Obsolete
org-glast-profile			Obsolete
datacatalog-web			Obsolete
org-glast-datamonitoring			Obsolete
org-glast-datamonitoring-web			Obsolete
org-glast-trendable-db			Obsolete
org-glast-pipeline-log			Obsolete
org-glast-pipeline-xml			Obsolete
org-glast-pipeline-core			Obsolete
org-glast-batch			Obsolete