[GUMP@lsd]: depot/depot-update-ant-sample-vfs failed
To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project depot-update-ant-sample-vfs has an issue affecting its community integration. The current state is 'Failed', for reason 'Build Failed' Full details are available at: http://lsd.student.utwente.nl/gump/depot/depot-update-ant-sample-vfs/index.html That said, some snippets follow: Gump provided these annotations: - Info - Dependency on ant exists, no need to add for property ant.home. - Info - Failed with reason build failed Gump performed this work: http://lsd.student.utwente.nl/gump/depot/depot-update-ant-sample-vfs/gump_work/build_depot_depot-update-ant-sample-vfs.html Work Name: build_depot_depot-update-ant-sample-vfs (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 8 seconds Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main -debug -Dgump.merge=/data3/gump/gump-install/work/merge.xml -Dbuild.sysclasspath=only -Dant.home=/data3/gump/ant/dist -f build-ant-sample.xml gump [Working Directory: /data3/gump/depot/update] CLASSPATH : /usr/java/j2sdk1.4.2_04/lib/tools.jar:/data3/gump/depot/update/dist/depot-update-gump-20040504.jar:/data3/gump/ant/dist/lib/ant-stylebook.jar:/data3/gump/ant/dist/lib/ant-jmf.jar:/data3/gump/ant/dist/lib/ant-swing.jar:/data3/gump/ant/dist/lib/ant-junit.jar:/data3/gump/ant/dist/lib/ant-launcher.jar:/data3/gump/ant/dist/lib/ant-xalan2.jar:/data3/gump/ant/dist/lib/ant-trax.jar:/data3/gump/ant/dist/lib/ant.jar:/data3/gump/ant/dist/lib/ant-nodeps.jar:/data3/gump/depot/version/dist/depot-version-gump-20040504.jar:/data3/gump/depot/common/dist/depot-common-gump-20040504.jar:/data3/gump/antworks-importer/dist/antworks-importer-0.1-gump-20040504.jar:/data3/gump/jakarta-regexp/build/jakarta-regexp-20040504.jar:/data3/gump/ant/bootstrap/lib/ant-launcher.jar:/data3/gump/ant/bootstrap/lib/ant.jar:/data3/gump/jakarta-commons/httpclient/dist/commons-httpclient.jar:/data3/gump/commons-vfs/target/commons-vfs-20040504.jar- [repotool] TagId : lib [repotool] RefId : null [repotool] Child :org.apache.depot.update.repository.DefaultRepository is set, for the Parent org.apache.depot.update.repository.RepositorySet [repotool] Attribute :VirtualResourceLocator is set [repotool] Attribute :RepositoryAttribute is set [repotool] RepositorySet: default BUILD FAILED java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory at org.apache.tools.ant.Project.executeTarget(Project.java:1221) at org.apache.tools.ant.Project.executeTargets(Project.java:1060) at org.apache.tools.ant.Main.runBuild(Main.java:666) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.Main.start(Main.java:151) at org.apache.tools.ant.Main.main(Main.java:234) Caused by: java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory at org.apache.commons.httpclient.HttpClient.clinit(HttpClient.java:65) at org.apache.depot.update.util.net.http.HttpClientUserAgent.init(HttpClientUserAgent.java:44) at org.apache.depot.update.protocols.impl.HttpClientProtocolOperationsProvider.init(HttpClientProtocolOperationsProvider.java:48) at org.apache.depot.update.protocols.ProtocolOperationsManager.registerProvider(ProtocolOperationsManager.java:71) at org.apache.depot.update.protocols.DefaultProtocolOperationsManager.init(DefaultProtocolOperationsManager.java:49) at org.apache.depot.update.impl.ResourceUpdaterContext.getDefaultContext(ResourceUpdaterContext.java:76) at org.apache.depot.update.ant.task.RepositoryToolTask.execute(RepositoryToolTask.java:83) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:268) at org.apache.tools.ant.Task.perform(Task.java:363) at org.apache.tools.ant.Target.execute(Target.java:321) at org.apache.tools.ant.Target.performTasks(Target.java:348) at org.apache.tools.ant.Project.executeTarget(Project.java:1212) ... 5 more --- Nested Exception --- java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory at org.apache.commons.httpclient.HttpClient.clinit(HttpClient.java:65) at org.apache.depot.update.util.net.http.HttpClientUserAgent.init(HttpClientUserAgent.java:44) at org.apache.depot.update.protocols.impl.HttpClientProtocolOperationsProvider.init(HttpClientProtocolOperationsProvider.java:48) at org.apache.depot.update.protocols.ProtocolOperationsManager.registerProvider(ProtocolOperationsManager.java:71) at org.apache.depot.update.protocols.DefaultProtocolOperationsManager.init(DefaultProtocolOperationsManager.java:49) at org.apache.depot.update.impl.ResourceUpdaterContext.getDefaultContext(ResourceUpdaterContext.java:76
[GUMP@lsd]: depot/depot-update-ant-sample-jdk failed
To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project depot-update-ant-sample-jdk has an issue affecting its community integration. The current state is 'Failed', for reason 'Build Failed' Full details are available at: http://lsd.student.utwente.nl/gump/depot/depot-update-ant-sample-jdk/index.html That said, some snippets follow: Gump provided these annotations: - Info - Dependency on ant exists, no need to add for property ant.home. - Info - Failed with reason build failed Gump performed this work: http://lsd.student.utwente.nl/gump/depot/depot-update-ant-sample-jdk/gump_work/build_depot_depot-update-ant-sample-jdk.html Work Name: build_depot_depot-update-ant-sample-jdk (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 8 seconds Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main -debug -Dgump.merge=/data3/gump/gump-install/work/merge.xml -Dbuild.sysclasspath=only -Dant.home=/data3/gump/ant/dist -f build-ant-sample.xml gump [Working Directory: /data3/gump/depot/update] CLASSPATH : /usr/java/j2sdk1.4.2_04/lib/tools.jar:/data3/gump/depot/update/dist/depot-update-gump-20040504.jar:/data3/gump/ant/dist/lib/ant-stylebook.jar:/data3/gump/ant/dist/lib/ant-jmf.jar:/data3/gump/ant/dist/lib/ant-swing.jar:/data3/gump/ant/dist/lib/ant-junit.jar:/data3/gump/ant/dist/lib/ant-launcher.jar:/data3/gump/ant/dist/lib/ant-xalan2.jar:/data3/gump/ant/dist/lib/ant-trax.jar:/data3/gump/ant/dist/lib/ant.jar:/data3/gump/ant/dist/lib/ant-nodeps.jar:/data3/gump/depot/version/dist/depot-version-gump-20040504.jar:/data3/gump/depot/common/dist/depot-common-gump-20040504.jar:/data3/gump/antworks-importer/dist/antworks-importer-0.1-gump-20040504.jar:/data3/gump/jakarta-regexp/build/jakarta-regexp-20040504.jar:/data3/gump/ant/bootstrap/lib/ant-launcher.jar:/data3/gump/ant/bootstrap/lib/ant.jar- [repotool] TagId : lib [repotool] RefId : null [repotool] startElement : repository [repotool] Class : org.apache.depot.update.repository.DefaultRepository [repotool] TagId : lib [repotool] RefId : null [repotool] Child :org.apache.depot.update.repository.DefaultRepository is set, for the Parent org.apache.depot.update.repository.RepositorySet [repotool] Attribute :VirtualResourceLocator is set [repotool] Attribute :RepositoryAttribute is set [repotool] RepositorySet: default BUILD FAILED java.lang.NoClassDefFoundError: org/apache/commons/httpclient/HttpMethod at org.apache.tools.ant.Project.executeTarget(Project.java:1221) at org.apache.tools.ant.Project.executeTargets(Project.java:1060) at org.apache.tools.ant.Main.runBuild(Main.java:666) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.Main.start(Main.java:151) at org.apache.tools.ant.Main.main(Main.java:234) Caused by: java.lang.NoClassDefFoundError: org/apache/commons/httpclient/HttpMethod at org.apache.depot.update.protocols.impl.HttpClientProtocolOperationsProvider.init(HttpClientProtocolOperationsProvider.java:48) at org.apache.depot.update.protocols.ProtocolOperationsManager.registerProvider(ProtocolOperationsManager.java:71) at org.apache.depot.update.protocols.DefaultProtocolOperationsManager.init(DefaultProtocolOperationsManager.java:49) at org.apache.depot.update.impl.ResourceUpdaterContext.getDefaultContext(ResourceUpdaterContext.java:76) at org.apache.depot.update.ant.task.RepositoryToolTask.execute(RepositoryToolTask.java:83) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:268) at org.apache.tools.ant.Task.perform(Task.java:363) at org.apache.tools.ant.Target.execute(Target.java:321) at org.apache.tools.ant.Target.performTasks(Target.java:348) at org.apache.tools.ant.Project.executeTarget(Project.java:1212) ... 5 more --- Nested Exception --- java.lang.NoClassDefFoundError: org/apache/commons/httpclient/HttpMethod at org.apache.depot.update.protocols.impl.HttpClientProtocolOperationsProvider.init(HttpClientProtocolOperationsProvider.java:48) at org.apache.depot.update.protocols.ProtocolOperationsManager.registerProvider(ProtocolOperationsManager.java:71) at org.apache.depot.update.protocols.DefaultProtocolOperationsManager.init(DefaultProtocolOperationsManager.java:49) at org.apache.depot.update.impl.ResourceUpdaterContext.getDefaultContext(ResourceUpdaterContext.java:76) at org.apache.depot.update.ant.task.RepositoryToolTask.execute(RepositoryToolTask.java:83) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:268) at org.apache.tools.ant.Task.perform(Task.java:363) at org.apache.tools.ant.Target.execute(Target.java:321
[GUMP@lsd]: depot/depot-version-test failed
To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project depot-version-test has an issue affecting its community integration. The current state is 'Failed', for reason 'Build Failed' Full details are available at: http://lsd.student.utwente.nl/gump/depot/depot-version-test/index.html That said, some snippets follow: Gump provided these annotations: - Info - Failed with reason build failed - Info - Enable debug output, due to build failure. - Info - Project Reports in: /data3/gump/depot/version/build/depot-version/junit/results Gump performed this work: http://lsd.student.utwente.nl/gump/depot/depot-version-test/gump_work/build_depot_depot-version-test.html Work Name: build_depot_depot-version-test (Type: Build) State: Failed Elapsed: 0 hours, 4 minutes, 1 seconds Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/data3/gump/xml-xerces2/java/build/xercesImpl.jar:/data3/gump/xml-xerces2/java/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/data3/gump/gump-install/work/merge.xml -Dbuild.sysclasspath=only -Dant.home=/data3/gump/ant/dist -f build.xml test [Working Directory: /data3/gump/depot/version] CLASSPATH : /usr/java/j2sdk1.4.2_04/lib/tools.jar:/data3/gump/depot/version/build/depot-version/junit/classes:/data3/gump/depot/version/dist/depot-version-gump-20040504.jar:/data3/gump/ant/dist/lib/ant-stylebook.jar:/data3/gump/ant/dist/lib/ant-jmf.jar:/data3/gump/ant/dist/lib/ant-swing.jar:/data3/gump/ant/dist/lib/ant-junit.jar:/data3/gump/ant/dist/lib/ant-launcher.jar:/data3/gump/ant/dist/lib/ant-xalan2.jar:/data3/gump/ant/dist/lib/ant-trax.jar:/data3/gump/ant/dist/lib/ant.jar:/data3/gump/ant/dist/lib/ant-nodeps.jar:/data3/gump/depot/common/dist/depot-common-gump-20040504.jar:/data3/gump/antworks-importer/dist/antworks-importer-0.1-gump-20040504.jar:/data3/gump/ant/build/lib/ant-testutil.jar:/data3/gump/dist/junit/junit.jar- compile: junit.test: [echo] Testing... [copy] Copying 6 files to /data3/gump/depot/version/build/depot-version/junit/classes [copy] Copied 35 empty directories to 16 empty directories under /data3/gump/depot/version/build/depot-version/junit/classes [javac] Compiling 43 source files to /data3/gump/depot/version/build/depot-version/junit/classes [xslt] Processing /home/ajack/.antworks/antlets/junit-0.1/resources/dummy.xml to /data3/gump/depot/version/build/work/junit/test.xml [xslt] Loading stylesheet /home/ajack/.antworks/antlets/junit-0.1/resources/stylesheets/test.xsl test: [junit] Running org.apache.depot.version.VersionRuntimeTests [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 3.236 sec [junit] Testsuite: org.apache.depot.version.VersionRuntimeTests [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 3.236 sec [junit] Testcase: testEquality took 0.238 sec [junit] Testcase: testInequality took 0.003 sec [junit] Testcase: testAPICalls took 1.648 sec [junit] Testcase: testResolve took 1.184 sec [junit] Running org.apache.depot.version.ant.available.VersionAvailableTaskTest [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 223.375 sec [junit] Testsuite: org.apache.depot.version.ant.available.VersionAvailableTaskTest [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 223.375 sec [junit] - Standard Output --- [junit] Ant Output: [junit] - --- [junit] Testcase: testExistence took 5.243 sec [junit] Testcase: testAbsence took 3.47 sec [junit] Testcase: testHigher took 214.496 sec [junit] Caused an ERROR [junit] java.lang.OutOfMemoryError [junit] java.lang.OutOfMemoryError [junit] at org.apache.depot.version.ant.available.VersionAvailableTaskTest.testHigher(VersionAvailableTaskTest.java:55) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] Caused by: java.lang.OutOfMemoryError [junit] --- Nested Exception --- [junit] java.lang.OutOfMemoryError BUILD FAILED /home/ajack/.antworks/antlets/junit-0.1/xbuild.xml:120: The following error occurred while executing this line: /data3/gump/depot/version/build/work/junit/test.xml:7: Test org.apache.depot.version.ant.available.VersionAvailableTaskTest failed Total time: 3 minutes 58 seconds - To subscribe to this information via syndicated feeds: RSS: http://lsd.student.utwente.nl/gump/depot/depot-version-test/rss.xml Atom: http://lsd.student.utwente.nl/gump/depot/depot
Re: [GUMP@lsd]: depot/depot-version-test failed
Seems wacky. Anybody got a clue where to start? regards Adam [junit] Testcase: testExistence took 5.243 sec [junit] Testcase: testAbsence took 3.47 sec [junit] Testcase: testHigher took 214.496 sec [junit] Caused an ERROR [junit] java.lang.OutOfMemoryError [junit] java.lang.OutOfMemoryError [junit] at org.apache.depot.version.ant.available.VersionAvailableTaskTest.testHigher(V ersionAvailableTaskTest.java:55) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) [junit] Caused by: java.lang.OutOfMemoryError [junit] --- Nested Exception --- [junit] java.lang.OutOfMemoryError
http://incubator.apache.org/depot/index.html
Would somebody mind updating this? [My version of forrest isn't new enough, and to get a new one I'll need to download forrest from SVN over modem, which I don't have time for this morning. The main reason I want it is because the closed left menu (projects) looks empty, and we look like we have an empty project. http://incubator.apache.org/depot/index.html I've added a table of our three sub-projects so folks can get some insights, and perhaps get interested. regards Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com
Wiring up MD5
Ok, here is what I am thinking, and I'm asking for feedback. We have an MD5 checksum file associated with an artefact we are wishing to download. We download/read the checksum, and then download the artefact, creating a checksum ourselves, comparing it to that original. Personally, I believe that we ought go to extreme measures to not leave any artefact on disk if it failed a check [even if we are CTRL-C'ed], since it is potentially tampered with. Even if we know it is bad, once taken out of the context of our code (and it'd be available on disk) others might become victim to it. As such I'd like to develop something like a stream that does the MD5 check as it is being written to, wrapped around some sort of tempfile(). If a stream isn't overkill, then the MD5 check could complete in the close() and if failed, perhaps destroy the file. We could attempt to re-write it with blanks, then try to delete it. Anybody got any thoughts on this? Anybody got any experience with similar things? regards, Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com
Re: http://incubator.apache.org/depot/index.html
Working on it now. Adam R. B. Jack wrote: Would somebody mind updating this? [My version of forrest isn't new enough, and to get a new one I'll need to download forrest from SVN over modem, which I don't have time for this morning. The main reason I want it is because the closed left menu (projects) looks empty, and we look like we have an empty project. http://incubator.apache.org/depot/index.html I've added a table of our three sub-projects so folks can get some insights, and perhaps get interested. regards Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com
Re: http://incubator.apache.org/depot/index.html
Done. Nick Chalko wrote: Working on it now. Adam R. B. Jack wrote: Would somebody mind updating this? [My version of forrest isn't new enough, and to get a new one I'll need to download forrest from SVN over modem, which I don't have time for this morning. The main reason I want it is because the closed left menu (projects) looks empty, and we look like we have an empty project. http://incubator.apache.org/depot/index.html I've added a table of our three sub-projects so folks can get some insights, and perhaps get interested. regards Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com
Re: Wiring up MD5
Adam R. B. Jack wrote: As such I'd like to develop something like a stream that does the MD5 check as it is being written to, wrapped around some sort of tempfile(). If a stream isn't overkill, then the MD5 check could complete in the close() and if failed, perhaps destroy the file. We could attempt to re-write it with blanks, then try to delete it. Anybody got any thoughts on this? Anybody got any experience with similar things? You know about java.security.DigestOutputStream and the similar java.crypt.MD5OutputStream from the cryptix package, right? It should be fairly straightforward to achieve what you want using either of these. -- Michael
