Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/GERONIMO-297 Here is an overview of the issue: --------------------------------------------------------------------- Key: GERONIMO-297 Summary: Build environment for all geronimo-related projects Type: New Feature Status: Unassigned Priority: Major Project: Apache Geronimo Components: buildsystem Versions: 1.0-M3 Assignee: Reporter: David Jencks Created: Wed, 15 Sep 2004 1:34 PM Updated: Wed, 15 Sep 2004 1:34 PM Description: It is now easy to work on all major geronimo-related projects in one maven build environment. There are also some features to make it easier to assure that all versions are synchronized accross all these projects. 1. Check out geronimo and cd geronimo/trunk 2. Edit project.properties or override with an appropriate build.properties to reflect your committer status on the associated projects. 3. run maven getotherprojects. This will check out activemq, howl, openejb, tranql, and tranql-connector. 4. run maven complete-rebuild This will delete the local repositories for these projects, do multiproject:clean, and multiproject:install. After you have all the external dependencies for all projects, you should run with -o so, within these projects, only artifacts just built can be used or found. Due to peculiarities with installing plugins, you may have to run this twice to get a successful build. Also, you may need -Dmaven.test.failure.ignore=true since, e.g., the activemq integration tests are not passing right now. 5. For normal building of all projects at once, run maven multiproject:install. Possible enhancements: 1. a scm update goal to update all projects from their respective repositories 2. getting maven multiproject:site to work. I don't understand the current failure. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
