geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anita Kulshreshtha (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Date Tue, 07 Mar 2006 15:58:39 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12369255 ] 

Anita Kulshreshtha commented on GERONIMO-851:
---------------------------------------------

These instructions are same as in security module :
This is the build order -
cd modules/util mvn install
cd ../system mvn -Dmaven.test.skip=true install , After building the system, comment it out
in the parent pom.
cd ..\j2ee mvn install
apply this patch and the j2ee-schema patch
cd ../.. top level mvn install, the build will fail at security
cd ../security Djava.security.auth.login.config=src/test-data/data/login.config -Dlog4j.configuration=file:log4j.properties
Remember to comment out security module, and run the build from the top level until done!

..........................................................
and finally stopped at 

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
[surefire] Running org.apache.geronimo.derby.DerbySystemGBeanTest
[surefire] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 7.907 sec <<<<<<<<
FAILURE !!
[INFO] ----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ----------------------------------------------------------------------------
[INFO] There are some test failure.
[INFO] ----------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 2 minutes 25 seconds
[INFO] Finished at: Tue Mar 07 10:50:55 EST 2006
[INFO] Final Memory: 16M/34M
[INFO] ----------------------------------------------------------------------------


Battery: org.apache.geronimo.derby.DerbySystemGBeanTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 7.907 sec 

testCreateSystemUsingServerInfo(org.apache.geronimo.derby.DerbySystemGBeanTest)  Time elapsed:
7.86 sec  <<< FAILURE!

[ stdout ] ---------------------------------------------------------------



[ stderr ] ---------------------------------------------------------------



[ stacktrace ] -----------------------------------------------------------

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)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at 

> Move Geronimo Build to M2 (Maven 2)
> -----------------------------------
>
>          Key: GERONIMO-851
>          URL: http://issues.apache.org/jira/browse/GERONIMO-851
>      Project: Geronimo
>         Type: Task
>   Components: buildsystem
>     Reporter: John Sisson
>     Assignee: John Sisson
>      Fix For: 1.x
>  Attachments: parentpom.patch
>
> Created this issue to keep track of the status of work to move the Geronimo build to
Maven 2.  Does anyone know the status of this effort? I believe some work was done in OpenEJB?
When is the move to M2 planned for? 1.0 or 1.1
> FYI.. In June I attempted to use Maven 1.1 beta 1 to build geronimo and got some parse
exceptions in maven.  As a result, some small changes were made to some project.xml files
by David Jencks, which fixed the parse problem, but we then ran into another problem where
we were getting a java.lang.NoSuchMethodError in maven.  This should now be fixed using an
updated artifact plugin, see http://jira.codehaus.org/browse/MAVEN-1625 (but I have not verified
this).

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message