...
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
...