Hi, Just want to describe the current status of the migration for others to help them follow up and contribute in any way - send patches/comment/argue/etc. ;) I'll do my best to procees patches and answer questions as they come. It should also help everybody who's working on it sync'ing and moving on from the same point.
(Anita, Anders, Henri, Prasad, could you, please, confirm we're at the same point in the migration?) It describes the state of the repository as of today: $ svn info Path: . URL: https://svn.apache.org/repos/asf/geronimo/trunk Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 383911 Node Kind: directory Schedule: normal Last Changed Author: jlaskowski Last Changed Rev: 383906 Last Changed Date: 2006-03-07 16:29:45 +0100 (Tue, 07 Mar 2006) Properties Last Updated: 2006-03-01 00:44:58 +0100 (Wed, 01 Mar 2006) The Geronimo build requires Maven 2.0.2 with no additional configuration tweaks (there was a *false* alarm about having to use the daily build of M2). Modules are subprojects of the top-level project and thus the general configuration happens in the parent pom.xml (versions, repositories, properties, etc.) whereas the child poms merely reference them. The list of (possibly-partially) migrated submodules includes: [INFO] Geronimo [INFO] Geronimo :: Activation [INFO] Geronimo :: ActiveMQ Embedded RAR [INFO] Geronimo :: Kernel [INFO] Geronimo :: Common [INFO] Geronimo :: Interceptor [INFO] Geronimo :: Util [INFO] Geronimo :: System [INFO] Geronimo :: Management API [INFO] Geronimo :: Core [INFO] Geronimo :: J2EE [INFO] Geronimo :: Web Services [INFO] Geronimo :: Security [INFO] Geronimo :: Axis [INFO] Geronimo :: Transaction [INFO] Geronimo :: Naming [INFO] Geronimo :: Client [INFO] Geronimo :: Deployment [INFO] Geronimo :: Connector [INFO] Geronimo :: Deploy :: Common Config [INFO] Geronimo :: J2EE Schema [INFO] Geronimo :: Service :: Builder [INFO] Geronimo :: Security :: Builder [INFO] Geronimo :: J2EE :: Builder [INFO] Geronimo :: Naming :: Builder [INFO] Geronimo :: Test :: DDBeans [INFO] Geronimo :: Connector :: Builder [INFO] Geronimo :: Configuration Converter [INFO] Geronimo :: Web :: Builder [INFO] Geronimo :: Deploy :: JSR-88 [INFO] Geronimo :: Deploy :: CLI Tool [INFO] Geronimo :: Derby [INFO] Geronimo :: Directory [INFO] Geronimo :: Deploy :: Hot Deployer [INFO] Geronimo :: JavaMail Transport [INFO] Geronimo :: JMX Remoting [INFO] Geronimo :: Mail [INFO] Geronimo :: Scripts [INFO] Geronimo :: Session [INFO] Geronimo :: Spring [INFO] Geronimo :: Timer Each module has its own subtask of http://issues.apache.org/jira/browse/GERONIMO-851, which is the JIRA main task for the M2 migration. The migration is meant to be done once the task has been closed. You can watch it so you'll be notified when it's happened (login to JIRA and use Watch link in the Operations of the left-hand side pane). You execute the build using the m2 standard phases - install, test, verify, clean. Of course the first time you're building it, you'll need to do it connected to the Net as there're lots of dependencies to be downloaded. There's a feature of the build so that you don't need to execute the whole build while you're working on a module. It's done via a profile specified in the top-level pom and is initialized by module property. Run mvn -Dmodule=<module> to execute the build of the specified <module>. Be sure to run it from within the top directory of the sources and the module itself. Some tests depend on physical resources like specific directory locations and files. Having written all this, we're failing on the derby module due to a non-working tests. Executing M2 finishes with the following test error: $ mvn -o clean install ... ------------------------------------------------------- T E S T S ------------------------------------------------------- [surefire] Running org.apache.geronimo.derby.DerbySystemGBeanTest log4j:WARN No appenders could be found for logger (DerbySystem). log4j:WARN Please initialize the log4j system properly. [surefire] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 7.781 sec <<<<<<<< FAILURE !! [INFO] ---------------------------------------------------------------------------- [ERROR] BUILD ERROR [INFO] ---------------------------------------------------------------------------- because of junit.framework.AssertionFailedError at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.apache.geronimo.derby.DerbySystemGBeanTest.testCreateSystemUsingServerInfo(DerbySystemGBeanTest.java:46) ... Hopefully, I didn't miss anything. Jacek -- Jacek Laskowski http://www.laskowski.org.pl
