Gump PMC Report
Infrastructure: * we've moved off of Brutus and are now spread over three machines. vmgump.apache.org is a VMWare instance on Loki, gump.zones.apache.org a Solaris zone on helios and gump.osuosl.org a MacOS X server of the Oregon State University that we can use. Many Thanks! * vmgump will become our primary machine for now, we are slowly progressing to the state of stability we had on brutus. * the other instances are not yet fully up and running. Technical: * Work continues on Gump3. It is slowly and steadily progressing into a codebase that does useful stuff. Other: * Nick Chalko has taken a leave of absence from the PMC, we hope to get him back next year. * still all Apache committers have access to metadata in CVS. * no releases. * There are three proposed Summer of Code projects for Gump, all focused on Gump3 development. Mentors include Scott Sanders, Adam Jack and Leo Simons. Since Gump is one of the few python-based projects in the programme, we expect some of these will be successfully followed up on. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/project jakarta-bsf.xml jakarta-ecs.xml jakarta-hivemind.xml
This will require us to remove the checked out source trees. I'll do so once the current run has come past the three directories. I had to manually kill a bunch of processes and remove lock files since the 6pm run didn't kill all childs, or so it seemed. There have been five lock files and about 10 python processes I had to remove in order to get the 0am Gump run unstuck. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PATCH][Gump] your definitions break Gump builds
Hi all, your own project definitions of commons-javaflow, commons-jci and lately spring break the Gump supplied definitions. We've been building svn trunk of commons-jci for weeks now, but it gets listed as failed because it doesn't produce a jar with your name. spring is an installed package and has been for quite some time, even before you added a defintion. The appendend patch simply removes the three project definitions, if this is not the correct way to deal with it, please at least rename your projects. Also, in the case of jci and javaflow, this is a repeated request, see http://marc.theaimsgroup.com/?l=xml-cocoon-devm=111468255224092w=2. Please let me know if I'm not following the correct protocol here. Cheers Stefan Index: gump.xml === --- gump.xml(revision 190800) +++ gump.xml(working copy) @@ -20,7 +20,7 @@ | | $Id$ | -| see http://brutus.apache.org/gump/public/buildLog.html +| see http://vmgump.apache.org/gump/public/buildLog.html | for already existing projects | +-- @@ -1530,18 +1530,6 @@ jar name=lib/optional/daisy-util-1.1.jar/ /project - project name=commons-javaflow -packageorg.apache.commons.javaflow/package -home nested=lib/optional/ -jar name=commons-javaflow-0.1-dev.jar/ - /project - - project name=commons-jci -packageorg.apache.jci/package -home nested=lib/core/ -jar name=commons-jci-r159148.jar/ - /project - project name=jcr packagejavax.jcr/package jar name=lib/optional/jcr-0.16.4.jar/ @@ -1553,8 +1541,4 @@ jar name=lib/optional/jackrabbit-20050422T153417.jar/ /project - project name=spring -packageorg.springframework/package -jar name=lib/optional/spring-1.1.5.jar/ - /project /module - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PATCH][Gump] your definitions break Gump builds
Stefan, I've committed this patch to Cocoon trunk. I presume that is the correct place. Regards, Upayavira Stefan Bodewig wrote: Hi all, your own project definitions of commons-javaflow, commons-jci and lately spring break the Gump supplied definitions. We've been building svn trunk of commons-jci for weeks now, but it gets listed as failed because it doesn't produce a jar with your name. spring is an installed package and has been for quite some time, even before you added a defintion. The appendend patch simply removes the three project definitions, if this is not the correct way to deal with it, please at least rename your projects. Also, in the case of jci and javaflow, this is a repeated request, see http://marc.theaimsgroup.com/?l=xml-cocoon-devm=111468255224092w=2. Please let me know if I'm not following the correct protocol here. Cheers Stefan Index: gump.xml === --- gump.xml(revision 190800) +++ gump.xml(working copy) @@ -20,7 +20,7 @@ | | $Id$ | -| see http://brutus.apache.org/gump/public/buildLog.html +| see http://vmgump.apache.org/gump/public/buildLog.html | for already existing projects | +-- @@ -1530,18 +1530,6 @@ jar name=lib/optional/daisy-util-1.1.jar/ /project - project name=commons-javaflow -packageorg.apache.commons.javaflow/package -home nested=lib/optional/ -jar name=commons-javaflow-0.1-dev.jar/ - /project - - project name=commons-jci -packageorg.apache.jci/package -home nested=lib/core/ -jar name=commons-jci-r159148.jar/ - /project - project name=jcr packagejavax.jcr/package jar name=lib/optional/jcr-0.16.4.jar/ @@ -1553,8 +1541,4 @@ jar name=lib/optional/jackrabbit-20050422T153417.jar/ /project - project name=spring -packageorg.springframework/package -jar name=lib/optional/spring-1.1.5.jar/ - /project /module - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PATCH][Gump] your definitions break Gump builds
On Thu, 16 Jun 2005, Upayavira [EMAIL PROTECTED] wrote: I've committed this patch to Cocoon trunk. Many thanks. I presume that is the correct place. Until the Cocoon project is annoyed enough by our patches and moves the descriptor over to Gump land, I think it is. 8-) Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PATCH][Gump] your definitions break Gump builds
Stefan Bodewig wrote: On Thu, 16 Jun 2005, Upayavira [EMAIL PROTECTED] wrote: I've committed this patch to Cocoon trunk. Many thanks. I presume that is the correct place. Until the Cocoon project is annoyed enough by our patches and moves the descriptor over to Gump land, I think it is. 8-) Stefan, it's not a matter of being annoyed enough (we are already!), it's the fact that cocoon needs that file at build time. Now, I would be totally in favor of granting the gump committers commit access to the cocoon project. -- Stefano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem running Apache Gump [vmgump-public]
There is a problem with run 'vmgump-public' (16062005_120001), location : http://vmgump.apache.org/gump/public The log ought be at: http://vmgump.apache.org/gump/public/gump_log.txt The last (up to) 50 lines of the log are : Perform Update on #[(2, 249)] : xml-xerces2 Perform Update on #[(4, 249)] : antlr Perform Update on #[(5, 249)] : jms Perform Update on #[(3, 249)] : xml-xalan Perform Update on #[(7, 249)] : jaf Perform Update on #[(6, 249)] : javamail Perform Update on #[(10, 249)] : packaged-jaxen Perform Update on #[(9, 249)] : jdbc Perform Update on #[(8, 249)] : javacc dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform Update on #[(11, 249)] : jsch Perform Update on #[(13, 249)] : picocontainer Perform Update on #[(12, 249)] : dougLea dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform Update on #[(14, 249)] : jsse Perform Update on #[(15, 249)] : jce Perform Update on #[(16, 249)] : jakarta-velocity dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform SVN Update on #[(16, 249)] : jakarta-velocity Perform Update on #[(17, 249)] : xdoclet Perform Update on #[(18, 249)] : xjavadoc Failed to checkout/update module: jakarta-velocity Perform Update on #[(19, 249)] : ejb Perform Update on #[(20, 249)] : mockobjects dynagumper.py processModule: need to implement module event processing Perform Update on #[(21, 249)] : java-xml-pack Perform Update on #[(22, 249)] : relaxng dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform Update on #[(23, 249)] : junitperf dynagumper.py processModule: need to implement module event processing Perform Update on #[(24, 249)] : xml-xindice dynagumper.py processModule: need to implement module event processing Perform Update on #[(25, 249)] : apr Perform SVN Update on #[(25, 249)] : apr Perform Update on #[(26, 249)] : snacc4j dynagumper.py processModule: need to implement module event processing Perform Update on #[(27, 249)] : aspectj dynagumper.py processModule: need to implement module event processing Process Exit Code : 139 -- Gump Version: 2.0.2-alpha-0003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem running Apache Gump [vmgump-public]
There is a problem with run 'vmgump-public' (16062005_120001), location : http://vmgump.apache.org/gump/public The log ought be at: http://vmgump.apache.org/gump/public/gump_log.txt The last (up to) 50 lines of the log are : Perform Update on #[(2, 249)] : xml-xerces2 Perform Update on #[(4, 249)] : antlr Perform Update on #[(5, 249)] : jms Perform Update on #[(3, 249)] : xml-xalan Perform Update on #[(7, 249)] : jaf Perform Update on #[(6, 249)] : javamail Perform Update on #[(10, 249)] : packaged-jaxen Perform Update on #[(9, 249)] : jdbc Perform Update on #[(8, 249)] : javacc dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform Update on #[(11, 249)] : jsch Perform Update on #[(13, 249)] : picocontainer Perform Update on #[(12, 249)] : dougLea dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform Update on #[(14, 249)] : jsse Perform Update on #[(15, 249)] : jce Perform Update on #[(16, 249)] : jakarta-velocity dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform SVN Update on #[(16, 249)] : jakarta-velocity Perform Update on #[(17, 249)] : xdoclet Perform Update on #[(18, 249)] : xjavadoc Failed to checkout/update module: jakarta-velocity Perform Update on #[(19, 249)] : ejb Perform Update on #[(20, 249)] : mockobjects dynagumper.py processModule: need to implement module event processing Perform Update on #[(21, 249)] : java-xml-pack Perform Update on #[(22, 249)] : relaxng dynagumper.py processModule: need to implement module event processing dynagumper.py processModule: need to implement module event processing Perform Update on #[(23, 249)] : junitperf dynagumper.py processModule: need to implement module event processing Perform Update on #[(24, 249)] : xml-xindice dynagumper.py processModule: need to implement module event processing Perform Update on #[(25, 249)] : apr Perform SVN Update on #[(25, 249)] : apr Perform Update on #[(26, 249)] : snacc4j dynagumper.py processModule: need to implement module event processing Perform Update on #[(27, 249)] : aspectj dynagumper.py processModule: need to implement module event processing Process Exit Code : 139 -- Gump Version: 2.0.2-alpha-0003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (GUMP-136) Bad XML causes Gump3 to crash
[ http://issues.apache.org/jira/browse/GUMP-136?page=all ] Leo Simons closed GUMP-136: --- Fix Version: Gump3-alpha-4 Resolution: Fixed Assign To: Leo Simons Fixed with svn commit 190980. Bad XML causes Gump3 to crash - Key: GUMP-136 URL: http://issues.apache.org/jira/browse/GUMP-136 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Leo Simons Fix For: Gump3-alpha-4 If any included (via 'href') XML is bad, Gump exits with an XML parser exception. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-138) Modules dropped (due to missing Repository) causes a crash.
[ http://issues.apache.org/jira/browse/GUMP-138?page=all ] Leo Simons reassigned GUMP-138: --- Assign To: Adam Jack Modules dropped (due to missing Repository) causes a crash. --- Key: GUMP-138 URL: http://issues.apache.org/jira/browse/GUMP-138 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Adam Jack Fix For: Gump3-alpha-3 Module dropped due to missing repository (e.g. for packaged??) causes later crash. 16:53:43 DEBUG Converting project definition 'xml-xercesImpl' into objectorm. 16:53:43 ERROR Fatal error during run! Traceback (most recent call last): File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\__init__.py, line 22 6, in run workspace = self.workspace_objectifier.get_workspace(domtree) File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 362, in get_w orkspace File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 403, in _crea te_projects File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 395, in _find _module_for_project KeyError: u'xml-xerces2' DEBUG: Run completed! DEBUG: Cleaning up child processes. This may take up to a little over 400 second s. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-122) Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase)
[ http://issues.apache.org/jira/browse/GUMP-122?page=all ] Leo Simons reassigned GUMP-122: --- Assign To: Adam Jack Unit test FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Key: GUMP-122 URL: http://issues.apache.org/jira/browse/GUMP-122 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-4 Environment: Cygwin Reporter: Leo Simons Assignee: Adam Jack Fix For: Gump3-alpha-4 I'd try to fix it, but I only have an hour free want to work on something else. regards Adam == FAIL: test_do_script (testPluginBuilder.BuilderTestCase) -- Traceback (most recent call last): File f:\data\Python\Gump3-SVN\gump\test\testPluginBuilder.py, line 62, in te st_do_script AssertionError: 'RESULT\n' != 'c:\\winnt\\temp\\tmpiv76ad\\w\\r\\m\\dobuild' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n -- Ran 52 tests in 11.857s FAILED (failures=1) == OVERALL FAILED (total failures=1) -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-138) Modules dropped (due to missing Repository) causes a crash.
[ http://issues.apache.org/jira/browse/GUMP-138?page=all ] Leo Simons reassigned GUMP-138: --- Assign To: Leo Simons (was: Adam Jack) Modules dropped (due to missing Repository) causes a crash. --- Key: GUMP-138 URL: http://issues.apache.org/jira/browse/GUMP-138 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Leo Simons Fix For: Gump3-alpha-3 Module dropped due to missing repository (e.g. for packaged??) causes later crash. 16:53:43 DEBUG Converting project definition 'xml-xercesImpl' into objectorm. 16:53:43 ERROR Fatal error during run! Traceback (most recent call last): File f:\data\Python\Gump3-SVN\pygump\python\gump\engine\__init__.py, line 22 6, in run workspace = self.workspace_objectifier.get_workspace(domtree) File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 362, in get_w orkspace File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 403, in _crea te_projects File f:\data\Python\Gump3-SVN\gump\engine\objectifier.py, line 395, in _find _module_for_project KeyError: u'xml-xerces2' DEBUG: Run completed! DEBUG: Cleaning up child processes. This may take up to a little over 400 second s. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-139) module project fails, it needs to be module project module
[ http://issues.apache.org/jira/browse/GUMP-139?page=all ] Leo Simons reassigned GUMP-139: --- Assign To: Leo Simons module project fails, it needs to be module project module --- Key: GUMP-139 URL: http://issues.apache.org/jira/browse/GUMP-139 Project: Gump Type: Bug Components: Python-based Gump Versions: Gump3-alpha-3 Reporter: Adam Jack Assignee: Leo Simons This might be considered support for 0.4 metadata. Normalizer:_get_list_merged_by_name returns cloned nodes --- and those nodes are w/o a parent. As such Normalizer:_find_module_containing_node fails when looking for the parent module. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PATCH][Gump] your definitions break Gump builds
On Thu, 16 Jun 2005, Stefano Mazzocchi [EMAIL PROTECTED] wrote: it's not a matter of being annoyed enough (we are already!), it's the fact that cocoon needs that file at build time. Hmm, so why don't you realize that you have a typo in it for many days? Like when you rename a jar but forget to update the descriptor? Now, I would be totally in favor of granting the gump committers commit access to the cocoon project. Should be quite trivial to add a rule to asf-authorization that grants rw to @gump for just that file, at least I think it allows file-granularity. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]