You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "John Sisson (JIRA)" <de...@geronimo.apache.org> on 2005/08/04 07:00:41 UTC
[jira] Created: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
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
Fix For: 1.0
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
[jira] Assigned: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=all ]
John Sisson reassigned GERONIMO-851:
------------------------------------
Assign To: John Sisson
> 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.0
>
> 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
[jira] Updated: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=all ]
Matt Hogstrom updated GERONIMO-851:
-----------------------------------
Fix Version: 1.x
(was: 1.0)
Moving to 1.x
> 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
>
> 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
[jira] Assigned: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=all ]
Jacek Laskowski reassigned GERONIMO-851:
----------------------------------------
Assign To: Jacek Laskowski (was: John Sisson)
> 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: Jacek Laskowski
> 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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Bruce Snyder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12319053 ]
Bruce Snyder commented on GERONIMO-851:
---------------------------------------
Yes, I'm interested in helping with this effort. I was going to go through a conversion of Castor's Maven build from Maven 1 to Maven 2 before pursuing this effort. Castor's Maven build is very straightforward and far less complex than Geronimo's multiproject Maven build. My assumption is that the conversion of Castor's Maven build will be a good preparation step to the conversion of the Geronimo build.
> 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.0
>
> 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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12368450 ]
Prasad Kashyap commented on GERONIMO-851:
-----------------------------------------
Tracking the migration work effort here -
http://opensource2.atlassian.com/confluence/oss/display/GERONIMO/Migration+to+Maven2
> 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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12369259 ]
Anita Kulshreshtha commented on GERONIMO-851:
---------------------------------------------
directory is failing because of -
[INFO] Failed to resolve artifact.
required artifacts missing:
xmlbeans:xmlbeans-jsr173-api:jar:2.0-dev
for the artifact:
org.apache.geronimo:geronimo-directory:jar:1.2-SNAPSHOT
After commenting it out the build completes!
[INFO] Reactor Summary:
[INFO] ----------------------------------------------------------------------------
[INFO] Geronimo ............................................... SUCCESS [3.735s]
[INFO] Geronimo :: Activation ................................. SUCCESS [2.578s]
[INFO] Geronimo :: ActiveMQ Embedded RAR ...................... SUCCESS [16.297s]
[INFO] Geronimo :: Kernel ..................................... SUCCESS [9.016s]
[INFO] Geronimo :: Common ..................................... SUCCESS [3.640s]
[INFO] Geronimo :: Management API ............................. SUCCESS [0.735s]
[INFO] Geronimo :: Core ....................................... SUCCESS [0.625s]
[INFO] Geronimo :: J2EE ....................................... SUCCESS [2.296s]
[INFO] Geronimo :: Transaction ................................ SUCCESS [28.813s]
[INFO] Geronimo :: Interceptor ................................ SUCCESS [0.391s]
[INFO] Geronimo :: Naming ..................................... SUCCESS [1.281s]
[INFO] Geronimo :: Client ..................................... SUCCESS [1.094s]
[INFO] Geronimo :: Deployment ................................. SUCCESS [1.203s]
[INFO] Geronimo :: Connector .................................. SUCCESS [7.265s]
[INFO] Geronimo :: Deploy :: Common Config .................... SUCCESS [0.407s]
[INFO] Geronimo :: J2EE Schema ................................ SUCCESS [14.250s]
[INFO] Geronimo :: Service :: Builder ......................... SUCCESS [3.843s]
[INFO] Geronimo :: Security :: Builder ........................ SUCCESS [1.375s]
[INFO] Geronimo :: J2EE :: Builder ............................ SUCCESS [1.125s]
[INFO] Geronimo :: Naming :: Builder .......................... SUCCESS [2.688s]
[INFO] Geronimo :: Test :: DDBeans ............................ SUCCESS [1.672s]
[INFO] Geronimo :: Connector :: Builder ....................... SUCCESS [2.891s]
[INFO] Geronimo :: Configuration Converter .................... SUCCESS [0.406s]
[INFO] Geronimo :: Util ....................................... SUCCESS [2.375s]
[INFO] Geronimo :: Web :: Builder ............................. SUCCESS [3.172s]
[INFO] Geronimo :: Deploy :: JSR-88 ........................... SUCCESS [1.391s]
[INFO] Geronimo :: Deploy :: CLI Tool ......................... SUCCESS [1.015s]
[INFO] Geronimo :: JavaMail Transport ......................... SUCCESS [1.438s]
[INFO] Geronimo :: JMX Remoting ............................... SUCCESS [0.812s]
[INFO] Geronimo :: Mail ....................................... SUCCESS [1.985s]
[INFO] Geronimo :: Scripts .................................... SUCCESS [0.672s]
[INFO] Geronimo :: Session .................................... SUCCESS [1.453s]
[INFO] Geronimo :: Spring ..................................... SUCCESS [0.734s]
[INFO] Geronimo :: Timer ...................................... SUCCESS [1:21.312s]
[INFO] Geronimo :: Web Services ............................... SUCCESS [2.000s]
[INFO] ----------------------------------------------------------------------------
[INFO] ----------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 3 minutes 30 seconds
[INFO] Finished at: Tue Mar 07 11:29:12 EST 2006
[INFO] Final Memory: 19M/35M
[INFO]
> 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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Updated: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=all ]
Anita Kulshreshtha updated GERONIMO-851:
----------------------------------------
Attachment: modules.patch
The earlier modules.patch is needed for building configs. For building just the modules use this patch. This does not alter the deploy-tool directory, and allows subsequent maven1 builds.
> Move Geronimo Build to M2 (Maven 2)
> -----------------------------------
>
> Key: GERONIMO-851
> URL: http://issues.apache.org/jira/browse/GERONIMO-851
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Components: buildsystem
> Reporter: John Sisson
> Assignee: Jacek Laskowski
> Fix For: 1.x
> Attachments: modules.patch, modules.patch, parentpom.patch, pom.patch, pom.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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12366407 ]
Jacek Laskowski commented on GERONIMO-851:
------------------------------------------
A page with the list of the dependencies and their status wrt POM v. 4.0.0 - http://wiki.apache.org/geronimo/Maven2Conversion.
> 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
>
> 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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12368944 ]
Anita Kulshreshtha commented on GERONIMO-851:
---------------------------------------------
GERONIMO-1693 is needed for all the builders.
> 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
[jira] Assigned: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=all ]
Jason Dillon reassigned GERONIMO-851:
-------------------------------------
Assignee: Jason Dillon (was: Jacek Laskowski)
> Move Geronimo Build to M2 (Maven 2)
> -----------------------------------
>
> Key: GERONIMO-851
> URL: http://issues.apache.org/jira/browse/GERONIMO-851
> Project: Geronimo
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: buildsystem
> Reporter: John Sisson
> Assigned To: Jason Dillon
> Fix For: 1.x
>
> Attachments: modules.patch, modules.patch, parentpom.patch, pom.patch, pom.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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "David DeWolf (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12319123 ]
David DeWolf commented on GERONIMO-851:
---------------------------------------
I just got done converting Pluto's 1.1 branch to maven to and would be willing to help out. I'm not that familiar with Geronimo's code base but maybe this would be a good opportunity to get my feet wet so that I can eventually help upgrade the web console to use Pluto 1.1. . .If you have any spefics you'd like me to submit patches for, let me know (ddewolf@apache.org). Otherwise I'll take a look a look and see where I may be able to help.
> 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.0
>
> 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
[jira] Updated: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=all ]
Anita Kulshreshtha updated GERONIMO-851:
----------------------------------------
Attachment: parentpom.patch
Tomcat version was updated to 5.5.15. This patch contains the updated parent pom.
> 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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12368024 ]
Jacek Laskowski commented on GERONIMO-851:
------------------------------------------
$ svn ci -m 'Upgrade Tomcat to the latest version used by Geronimo. Thanks Anita!' pom.xml
Sending pom.xml
Transmitting file data .
Committed revision 381438.
Thanks Anita!
One point is that your patch is made from incorrect directory (D:/) rather than from the main directory of Geronimo sources (D:/anita/geronimo/geronimo-1.1 in your particular case).
> 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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12368096 ]
Anita Kulshreshtha commented on GERONIMO-851:
---------------------------------------------
Thanks for pointing this out! This patch was created from geronimo-1.1 dir using TortoiseSVN!
IN last 2 weeks I have been bitten by these bugs in TortoiseSVN : duplicate files, missing files. I found this -
http://svn.haxx.se/tsvn/archive-2006-01/0305.shtml . I guess I am the only one using TortoiseSVN here. No more patches created via
TortoiseSVN!
> 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
[jira] Resolved: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=all ]
Jason Dillon resolved GERONIMO-851.
-----------------------------------
Fix Version/s: 1.2
(was: 1.x)
Resolution: Fixed
This is done for the most part... only a few pending items tracked by other issues.
> Move Geronimo Build to M2 (Maven 2)
> -----------------------------------
>
> Key: GERONIMO-851
> URL: http://issues.apache.org/jira/browse/GERONIMO-851
> Project: Geronimo
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: buildsystem
> Reporter: John Sisson
> Assigned To: Jason Dillon
> Fix For: 1.2
>
> Attachments: modules.patch, modules.patch, parentpom.patch, pom.patch, pom.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
[jira] Updated: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=all ]
Anita Kulshreshtha updated GERONIMO-851:
----------------------------------------
Attachment: pom.patch
This patch removes the legacy ibiblio repo. Since all the base modules have been migrated, this is not needed.
The legacy poms are auto generated and hence incomplete, they might break the build.
> 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: Jacek Laskowski
> Fix For: 1.x
> Attachments: parentpom.patch, pom.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
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by Bruce Snyder <br...@gmail.com>.
On 8/17/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
> Is it backwards compatible?
>
> IOW, can people that use M1 also still work?
No, a conversion from Maven 1 to Maven 2 is akin to a switch from
Maven 1 to makefiles. Users will need to install Maven 2 (aka m2) in
order to use a Maven 2 style of build.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by Jeff Genender <jg...@savoirtech.com>.
Whats your thoughts on creating a directory in each of the modules
called "m2" and begin the development there. I like what OpenEJB has
done in this effort.
Then when its all converted we can move the code up into each module and
get rid of the "old way".
This will allow us to piece meal it together, module by module.
Thoughts?
Alan D. Cabrera wrote:
> To be a little more specific, maven 1 and maven 2 can both work with
> maven 2 POMs. It's our non-standard jelly code that impedes our
> conversion. We need to enumerate where that code is, determine if there
> is an M2 replacement for it, it not decide if we need it and if we do,
> make a plug in or convert the code.
> It is my understanding that much of the jelly code is optimizations,
> e.g. don't run tests if they've already been run. The maven team is
> happy to make such optimizations a priority to include in M2.
>
> After the conversion, I hope that we have no more jelly.
>
>
> Regards,
> Alan
>
> Alan D. Cabrera wrote, On 8/17/2005 9:34 AM:
>
>> Normally, yes. Unfortunately there is a lot of jelly code out there.
>>
>> Geir Magnusson Jr. wrote, On 8/17/2005 9:15 AM:
>>
>>> Is it backwards compatible?
>>>
>>> IOW, can people that use M1 also still work?
>>
>>
>
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by Vadim Nasardinov <va...@redhat.com>.
On Wednesday 17 August 2005 13:58, Bruce Snyder wrote:
> > +10000000000000000000000000000000000000000000000000000000
>
> Wow, that number has 55 zeros - one zero higher than Septendecillion.
> Does anyone know if there's a name for that number? Maybe 10
> Septendecillion?
That is correct according to at least one Common Lisp implementation.
The Common Lisp FORMAT function gives you a way to convert integers to
their English names:
http://www.lispworks.com/documentation/HyperSpec/Body/f_format.htm
http://www.lispworks.com/documentation/HyperSpec/Body/22_cba.htm
So,
|CL-USER> (format nil "~r" 10000000000000000000000000000000000000000000000000000000)
|
|"ten septendecillion"
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by Bruce Snyder <br...@gmail.com>.
On 8/17/05, Alan D. Cabrera <li...@toolazydogs.com> wrote:
> Bruce Snyder wrote, On 8/17/2005 10:58 AM:
> On 8/17/05, Dain Sundstrom <da...@iq80.com> wrote:
>
>
> On Aug 17, 2005, at 9:42 AM, Alan D. Cabrera wrote:
>
>
>
> After the conversion, I hope that we have no more jelly.
>
> +10000000000000000000000000000000000000000000000000000000
>
> Wow, that number has 55 zeros - one zero higher than Septendecillion.
> Does anyone know if there's a name for that number? Maybe 10
> Septendecillion?
>
> Sundstromplex
;-)
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Bruce Snyder wrote, On 8/17/2005 10:58 AM:
>On 8/17/05, Dain Sundstrom <da...@iq80.com> wrote:
>
>
>>On Aug 17, 2005, at 9:42 AM, Alan D. Cabrera wrote:
>>
>>
>>
>>>After the conversion, I hope that we have no more jelly.
>>>
>>>
>>+10000000000000000000000000000000000000000000000000000000
>>
>>
>
>Wow, that number has 55 zeros - one zero higher than Septendecillion.
>Does anyone know if there's a name for that number? Maybe 10
>Septendecillion?
>
>
Sundstromplex
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by Bruce Snyder <br...@gmail.com>.
On 8/17/05, Dain Sundstrom <da...@iq80.com> wrote:
> On Aug 17, 2005, at 9:42 AM, Alan D. Cabrera wrote:
>
> > After the conversion, I hope that we have no more jelly.
>
> +10000000000000000000000000000000000000000000000000000000
Wow, that number has 55 zeros - one zero higher than Septendecillion.
Does anyone know if there's a name for that number? Maybe 10
Septendecillion?
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by Dain Sundstrom <da...@iq80.com>.
On Aug 17, 2005, at 9:42 AM, Alan D. Cabrera wrote:
> After the conversion, I hope that we have no more jelly.
+10000000000000000000000000000000000000000000000000000000
-dain
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by si...@insession.com.
"Geir Magnusson Jr." <ge...@apache.org> wrote on 18/08/2005 07:24:10 AM:
>
> On Aug 17, 2005, at 1:10 PM, Bruce Snyder wrote:
>
> > On 8/17/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
> >
> >
> >> I think we should consider choosing appropriate timing - it sounds
> >> like a big effort, and how does this fit into what we want to do w/
> >> M5, 1.0, etc I was going to suggest voting on even doing this, but I
> >> can't imagine that at *some* point in the future, we don't want to be
> >> on M2, so we will go there eventually. it's just a matter of when...
> >>
> >
> > Is there ever an appropriate time to overhaul the build? Not really.
>
> Sure there is. Foe example, in a commercial shop, I'd do it after a
> major release before knuckling down again.
>
> >
> > Is the proposed change in the best interest of the project and the
> > community? Yes.
>
> There's no objection from me on this. I'm just trying to kick off a
> conversation about priorities :)
I don't think M5 sounds like a realistic target. AFAIK, we were
originally aiming for M5 in August.
It would be helpful if we could identify JIRA issues that would benefit
from or need m2. What are the drivers for this work? Does GERONIMO-853
need m2, or is it a nice to have? Any issues that need m2 should be
linked to this (GERONIMO-851) issue.
Is there a JIRA for the work remaining on the assembly plugin (for maven
1)? Would it need or benefit from M2 (I seem to remember m2 being
mentioned)?
John
>
> geir
>
This e-mail message and any attachments may contain confidential,
proprietary or non-public information. This information is intended
solely for the designated recipient(s). If an addressing or transmission
error has misdirected this e-mail, please notify the sender immediately
and destroy this e-mail. Any review, dissemination, use or reliance upon
this information by unintended recipients is prohibited. Any opinions
expressed in this e-mail are those of the author personally.
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Aug 17, 2005, at 1:10 PM, Bruce Snyder wrote:
> On 8/17/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
>
>
>> I think we should consider choosing appropriate timing - it sounds
>> like a big effort, and how does this fit into what we want to do w/
>> M5, 1.0, etc I was going to suggest voting on even doing this, but I
>> can't imagine that at *some* point in the future, we don't want to be
>> on M2, so we will go there eventually. it's just a matter of when...
>>
>
> Is there ever an appropriate time to overhaul the build? Not really.
Sure there is. Foe example, in a commercial shop, I'd do it after a
major release before knuckling down again.
>
> Is the proposed change in the best interest of the project and the
> community? Yes.
There's no objection from me on this. I'm just trying to kick off a
conversation about priorities :)
geir
>
> Will this change be ready for release in M5? Good question ;-). I
> don't think this can be determined without digging in a bit.
>
> Are the people who have thrown their hat into the ring for working on
> this effort on the hook for any M5 related work that takes a higher
> priority? I'd like to get GERONIMO-693 and GERONIMO-871 tested and
> committed. Only after that will I begin work on the converstion to m2.
>
> Bruce
> --
> perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!
> G;6%I;\"YC;VT*"
> );'
>
> The Castor Project
> http://www.castor.org/
>
> Apache Geronimo
> http://geronimo.apache.org/
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by Bruce Snyder <br...@gmail.com>.
On 8/17/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
> I think we should consider choosing appropriate timing - it sounds
> like a big effort, and how does this fit into what we want to do w/
> M5, 1.0, etc I was going to suggest voting on even doing this, but I
> can't imagine that at *some* point in the future, we don't want to be
> on M2, so we will go there eventually. it's just a matter of when...
Is there ever an appropriate time to overhaul the build? Not really.
Is the proposed change in the best interest of the project and the
community? Yes.
Will this change be ready for release in M5? Good question ;-). I
don't think this can be determined without digging in a bit.
Are the people who have thrown their hat into the ring for working on
this effort on the hook for any M5 related work that takes a higher
priority? I'd like to get GERONIMO-693 and GERONIMO-871 tested and
committed. Only after that will I begin work on the converstion to m2.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
I think that some work can be done investigating where the jelly lies.
We can then add sub-tasks to track their conversion. All of this can be
done w/out interfering with the M5 release.
Regards,
Alan
Geir Magnusson Jr. wrote, On 8/17/2005 9:54 AM:
> Thx.
>
> I think we should consider choosing appropriate timing - it sounds
> like a big effort, and how does this fit into what we want to do w/
> M5, 1.0, etc I was going to suggest voting on even doing this, but I
> can't imagine that at *some* point in the future, we don't want to be
> on M2, so we will go there eventually. it's just a matter of when...
>
> geir
>
> On Aug 17, 2005, at 12:42 PM, Alan D. Cabrera wrote:
>
>
>> To be a little more specific, maven 1 and maven 2 can both work with
>> maven 2 POMs. It's our non-standard jelly code that impedes our
>> conversion. We need to enumerate where that code is, determine if
>> there is an M2 replacement for it, it not decide if we need it and
>> if we do, make a plug in or convert the code.
>> It is my understanding that much of the jelly code is optimizations,
>> e.g. don't run tests if they've already been run. The maven team is
>> happy to make such optimizations a priority to include in M2.
>>
>> After the conversion, I hope that we have no more jelly.
>>
>>
>> Regards,
>> Alan
>>
>> Alan D. Cabrera wrote, On 8/17/2005 9:34 AM:
>>
>>
>>
>>> Normally, yes. Unfortunately there is a lot of jelly code out there.
>>>
>>> Geir Magnusson Jr. wrote, On 8/17/2005 9:15 AM:
>>>
>>>
>>>
>>>> Is it backwards compatible?
>>>>
>>>> IOW, can people that use M1 also still work?
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by Matt Hogstrom <ma...@hogstrom.org>.
0817101064990bba@mail.gmail.com>
In-Reply-To: <7b...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MMS-Smtp-Program: Macallan-Mail-Solution; Version 4.6.0.1
X-MMS-Smtp-Auth: Authenticated As matt@hogstrom.org
X-MMS-Smtp-Mailer-Program: Macallan-Mail-Solution; Version 4.6.0.1
I'm trying to get my head around maven and the like so at least for me
this is the best way to learn it. I'll volunteer to help.
- Matt
Bruce Snyder wrote:
>On 8/17/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
>
>
>
>>I think we should consider choosing appropriate timing - it sounds
>>like a big effort, and how does this fit into what we want to do w/
>>M5, 1.0, etc I was going to suggest voting on even doing this, but I
>>can't imagine that at *some* point in the future, we don't want to be
>>on M2, so we will go there eventually. it's just a matter of when...
>>
>>
>
>Is there ever an appropriate time to overhaul the build? Not really.
>
>Is the proposed change in the best interest of the project and the
>community? Yes.
>
>Will this change be ready for release in M5? Good question ;-). I
>don't think this can be determined without digging in a bit.
>
>Are the people who have thrown their hat into the ring for working on
>this effort on the hook for any M5 related work that takes a higher
>priority? I'd like to get GERONIMO-693 and GERONIMO-871 tested and
>committed. Only after that will I begin work on the converstion to m2.
>
>Bruce
>
>
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
Thx.
I think we should consider choosing appropriate timing - it sounds
like a big effort, and how does this fit into what we want to do w/
M5, 1.0, etc I was going to suggest voting on even doing this, but I
can't imagine that at *some* point in the future, we don't want to be
on M2, so we will go there eventually. it's just a matter of when...
geir
On Aug 17, 2005, at 12:42 PM, Alan D. Cabrera wrote:
> To be a little more specific, maven 1 and maven 2 can both work
> with maven 2 POMs. It's our non-standard jelly code that impedes
> our conversion. We need to enumerate where that code is, determine
> if there is an M2 replacement for it, it not decide if we need it
> and if we do, make a plug in or convert the code.
> It is my understanding that much of the jelly code is
> optimizations, e.g. don't run tests if they've already been run.
> The maven team is happy to make such optimizations a priority to
> include in M2.
>
> After the conversion, I hope that we have no more jelly.
>
>
> Regards,
> Alan
>
> Alan D. Cabrera wrote, On 8/17/2005 9:34 AM:
>
>
>
>> Normally, yes. Unfortunately there is a lot of jelly code out there.
>>
>> Geir Magnusson Jr. wrote, On 8/17/2005 9:15 AM:
>>
>>
>>
>>> Is it backwards compatible?
>>>
>>> IOW, can people that use M1 also still work?
>>>
>>>
>>
>>
>>
>
>
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
To be a little more specific, maven 1 and maven 2 can both work with
maven 2 POMs. It's our non-standard jelly code that impedes our
conversion. We need to enumerate where that code is, determine if there
is an M2 replacement for it, it not decide if we need it and if we do,
make a plug in or convert the code.
It is my understanding that much of the jelly code is optimizations,
e.g. don't run tests if they've already been run. The maven team is
happy to make such optimizations a priority to include in M2.
After the conversion, I hope that we have no more jelly.
Regards,
Alan
Alan D. Cabrera wrote, On 8/17/2005 9:34 AM:
> Normally, yes. Unfortunately there is a lot of jelly code out there.
>
> Geir Magnusson Jr. wrote, On 8/17/2005 9:15 AM:
>
>> Is it backwards compatible?
>>
>> IOW, can people that use M1 also still work?
>
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Normally, yes. Unfortunately there is a lot of jelly code out there.
Geir Magnusson Jr. wrote, On 8/17/2005 9:15 AM:
> Is it backwards compatible?
>
> IOW, can people that use M1 also still work?
>
> geir
>
> On Aug 17, 2005, at 8:03 AM, John Sisson (JIRA) wrote:
>
>> [ http://issues.apache.org/jira/browse/GERONIMO-851?
>> page=comments#action_12319006 ]
>>
>> John Sisson commented on GERONIMO-851:
>> --------------------------------------
>>
>> I am looking into how we can split this work into subtasks. A
>> subtask per module is probably going overboard.
>>
>> Any other volunteers interested in helping with the move to m2?
>>
>>
>>> 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
>>> Fix For: 1.0
>>>
>>
>>
>>>
>>> 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
>>
>>
>
Re: [jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
Is it backwards compatible?
IOW, can people that use M1 also still work?
geir
On Aug 17, 2005, at 8:03 AM, John Sisson (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/GERONIMO-851?
> page=comments#action_12319006 ]
>
> John Sisson commented on GERONIMO-851:
> --------------------------------------
>
> I am looking into how we can split this work into subtasks. A
> subtask per module is probably going overboard.
>
> Any other volunteers interested in helping with the move to m2?
>
>
>> 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
>> Fix For: 1.0
>>
>
>
>>
>> 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
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12319006 ]
John Sisson commented on GERONIMO-851:
--------------------------------------
I am looking into how we can split this work into subtasks. A subtask per module is probably going overboard.
Any other volunteers interested in helping with the move to m2?
> 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
> Fix For: 1.0
>
> 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
[jira] Updated: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=all ]
Anita Kulshreshtha updated GERONIMO-851:
----------------------------------------
Attachment: pom.patch
modules.patch
This patch updates pom.xmls from the dead-1.2 trunk for the current trunk. the following changes have been made -
- parent pom -
- added asm, g-directory, g-jmx-remoting to dep mgmt section.
- corrected versions of all ${*Versions} to match etc/project.properties in the
trunk.
_commons-modeler version should be 1.2-GERONIMO-SNAPSHOT_
- need to check surefire version -
added this to surefire plugin configuration
<forkMode>once</forkMode>
<workingDirectory>${basedir}</workingDirectory>
- use this for maven-compiler-plugin
<source>1.4</source>
<target>1.4</target>
using ${maven.compile.source} does not seem to work!
- I am using m2-plugins for plugins directory, If you prefer plugins-m2, I will rename it when I submit the patch.
<module>plugins-m2/${plugin}</module>
- modules -
- general dependency pruning in all modules.
- kernel - include 'services' in the jar.
- added more ant code to build directories for the tests in system module.
- made changes to *-builder to include *-1.1-xsd in the schema and the jars.
-Checked in geronimo-dependency.xml files for axis, tomcat and jetty :(. Once the build gets going,
we can try to remove it.
> Move Geronimo Build to M2 (Maven 2)
> -----------------------------------
>
> Key: GERONIMO-851
> URL: http://issues.apache.org/jira/browse/GERONIMO-851
> Project: Geronimo
> Type: Task
> Security: public(Regular issues)
> Components: buildsystem
> Reporter: John Sisson
> Assignee: Jacek Laskowski
> Fix For: 1.x
> Attachments: modules.patch, parentpom.patch, pom.patch, pom.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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12367087 ]
Jacek Laskowski commented on GERONIMO-851:
------------------------------------------
$ svn ci maven.xml
Sending maven.xml
Transmitting file data .
Committed revision 379245.
With the revision, you can execute Maven2 together with the new Geronimo build based on Maven1.
+ The m2 property is to ignite the build of the kernel module using Maven2
+ The goal: m2 is to create a template to execute Maven2 commands via goal property
+ The execmvn goal is to execute Maven2 shell script either mvn.bat or mvn based on OS (it surely needs more appropriate OS names)
Run maven -Dm2=true new to build Geronimo with the new goal and execute mvn install on the kernel module
Run maven m2 to execute mvn install on the kernel module only
> 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
>
> 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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven
2)
Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12370944 ]
Jacek Laskowski commented on GERONIMO-851:
------------------------------------------
I'll hold it off until I have sorted out the issues I'm having with the security module. Looking into it.
> 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: Jacek Laskowski
> Fix For: 1.x
> Attachments: parentpom.patch, pom.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