[jira] [Resolved] (GUMP-155) Gump complains that the HiveMind build failed, when it does not
[ https://issues.apache.org/jira/browse/GUMP-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved GUMP-155. - Resolution: Invalid Gump complains that the HiveMind build failed, when it does not --- Key: GUMP-155 URL: https://issues.apache.org/jira/browse/GUMP-155 Project: Gump Issue Type: Bug Reporter: Howard M. Lewis Ship I get emails from Gump all the time that claim there's an error, but there's no indication of what the error is (notice that all the tests passed): To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at general@gump.apache.org. Project jakarta-hivemind has an issue affecting its community integration. This issue affects 3 projects, and has been outstanding for 61 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-hivemind : HiveMind is a services and configuration microkernel - jakarta-hivemind-library : HiveMind is a services and configuration microkernel - jakarta-tapestry : Component-based web application framework organized around i... Full details are available at: http://vmgump.apache.org/gump/public/jakarta-hivemind/jakarta-hivemind/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [hivemind-28092005.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-hivemind/jakarta-hivemind/gump_work/build_jakarta-hivemind_jakarta-hivemind.html Work Name: build_jakarta-hivemind_jakarta-hivemind (Type: Build) Work ended in a state of : Failed Elapsed: 42 secs Command Line: java -Djava.awt.headless=true -Dant.build.clonevm=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Djava.classes.dir=target/classes -Djunit-available=true -Djavacc.home=/usr/local/gump/packages/javacc-3.1 -Ddownload-warning-marker-displayed=true -Dtest.classes.dir=target/test-classes -Dproject.version=28092005 [Working Directory: /usr/local/gump/public/workspace/jakarta-hivemind/framework] CLASSPATH:
[jira] [Resolved] (GUMP-147) Complain if a project does not provide all the outputs it states
[ https://issues.apache.org/jira/browse/GUMP-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved GUMP-147. - Resolution: Fixed Fix Version/s: (was: Gump3-alpha-7) Complain if a project does not provide all the outputs it states Key: GUMP-147 URL: https://issues.apache.org/jira/browse/GUMP-147 Project: Gump Issue Type: New Feature Components: Python-based Gump Affects Versions: Gump3-alpha-7 Reporter: Leo Simons We should have a post-processing plugin (maybe one-per-output-type) that looks for successfully built projects, then goes and peeks if each and every of the outputs it specifies now actually exists (probably os.exists() and sometimes os.isfile() and os.isdir() if appropriate). If not, the plugin should mark the failure on the output. The logreporter should be modified to include this information with each project (this is probably a METADATA FAILURE), eg loop over all outputs for all projects and check_failure on each of them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] [Resolved] (GUMP-167) Add Mockito to Apache FOPs classpath
[ https://issues.apache.org/jira/browse/GUMP-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved GUMP-167. - Resolution: Fixed Should be on the way with http://svn.apache.org/viewvc?view=revisionrevision=1205332 We'll need to wait whether Mockito actually builds or whether we need to tweak its descriptor. Add Mockito to Apache FOPs classpath Key: GUMP-167 URL: https://issues.apache.org/jira/browse/GUMP-167 Project: Gump Issue Type: Bug Components: Infrastructure, Java-based Gump Reporter: Mehdi Houshmand Currently Gump fails the Junit tests for the FOP project with class not found errors. The classes in question are from Mockito which has recently been added as a test dependency, and I think it's because the mockito JAR hasn't been added to the metadata XML file (http://svn.apache.org/repos/asf/gump/metadata/project/xml-fop.xml). If so we need to add mockito and it's dependencies objenesis and hamcrest, I could however be missing something. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] [Resolved] (GUMP-166) Add fop-hyph.jar to Apache FOP's classpath
[ https://issues.apache.org/jira/browse/GUMP-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved GUMP-166. - Resolution: Fixed Add fop-hyph.jar as installed package Add fop-hyph.jar to Apache FOP's classpath -- Key: GUMP-166 URL: https://issues.apache.org/jira/browse/GUMP-166 Project: Gump Issue Type: Bug Components: Infrastructure Reporter: Vincent Hennebert Attachments: fop-hyph.jar FOP Hyphenation test cases are now run by default, but rely on an external jar that is not currently in the classpath in Gump. Would it be possible to add it? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
