[GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
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 gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 65 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-configuration-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/configuration/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/configuration/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/gump_work/build_apache-commons_commons-configuration-test.html Work Name: build_apache-commons_commons-configuration-test (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 47 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/configuration] M2_HOME: /opt/maven2 - Running org.apache.commons.configuration.TestHierarchicalConfigurationXMLReader Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec Running org.apache.commons.configuration.TestNullCompositeConfiguration Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.117 sec Running org.apache.commons.configuration.interpol.TestConfigurationInterpolator Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec Running org.apache.commons.configuration.interpol.TestEnvironmentLookup Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec Running org.apache.commons.configuration.interpol.TestExprLookup Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.configuration.interpol.TestConstantLookup Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Running org.apache.commons.configuration.TestPropertiesConfigurationLayout Tests run: 38, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.039 sec Running org.apache.commons.configuration.TestConfigurationConverter Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Running org.apache.commons.configuration.TestFileConfiguration Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.749 sec Running org.apache.commons.configuration.TestPatternSubtreeConfiguration Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running org.apache.commons.configuration.TestPropertyConverter Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec Running org.apache.commons.configuration.TestConfigurationMap Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.commons.configuration.reloading.TestManagedReloadingStrategy Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.commons.configuration.reloading.TestVFSFileChangedReloadingStrategy Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.015 sec Running org.apache.commons.configuration.reloading.TestFileChangedReloadingStrategy Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.02 sec Results : Failed tests: testValidation2(org.apache.commons.configuration.TestVFSConfigurationBuilder): The test key was not located Tests run: 1595, Failures: 1, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /srv/gump/public/workspace/apache-commons/configuration/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 45 seconds [INFO] Finished at: Sun Mar 25 07:18:30 UTC 2012 [INFO] Final
[GUMP@vmgump]: Project commons-proxy-test (in module apache-commons) failed
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 gene...@gump.apache.org. Project commons-proxy-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 52 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-proxy-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/proxy/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/gump_work/build_apache-commons_commons-proxy-test.html Work Name: build_apache-commons_commons-proxy-test (Type: Build) Work ended in a state of : Failed Elapsed: 11 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/proxy] M2_HOME: /opt/maven2 - Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.factory.util.TestMethodSignature Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.provider.TestConstantProvider Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec Running org.apache.commons.proxy.interceptor.filter.TestPatternFilter Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 sec Running org.apache.commons.proxy.interceptor.TestInterceptorChain Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec Running org.apache.commons.proxy.invoker.TestNullInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running org.apache.commons.proxy.exception.TestDelegateProviderException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.invoker.TestChainInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.186 sec Running org.apache.commons.proxy.exception.TestProxyFactoryException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running org.apache.commons.proxy.interceptor.filter.TestReturnTypeFilter Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.provider.TestBeanProvider Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Results : Tests in error: testInvalidHandlerName(org.apache.commons.proxy.invoker.TestXmlRpcInvoker) Tests run: 179, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 10 seconds [INFO] Finished at: Sun Mar 25 07:20:23 UTC 2012 [INFO] Final Memory: 24M/58M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/rss.xml - Atom:
[GUMP@vmgump]: Project commons-id (in module commons-sandbox) failed
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 gene...@gump.apache.org. Project commons-id has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 26 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-id : Commons Identifier Package Full details are available at: http://vmgump.apache.org/gump/public/commons-sandbox/commons-id/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole jar output [commons-id-25032012.jar] identifier set to project name -DEBUG- (Apache Gump generated) Apache Maven Properties in: /srv/gump/public/workspace/commons-sandbox/id/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-sandbox/id/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/commons-sandbox/id/project.properties -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-sandbox/commons-id/gump_work/build_commons-sandbox_commons-id.html Work Name: build_commons-sandbox_commons-id (Type: Build) Work ended in a state of : Failed Elapsed: 23 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/commons-sandbox/id] - [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.377 sec [junit] Running org.apache.commons.id.uuid.state.NodeTest [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.317 sec [junit] Running org.apache.commons.id.uuid.state.ReadOnlyResourceStateImplTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.448 sec [junit] Running org.apache.commons.id.uuid.state.ReadWriteFileStateImplTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.452 sec [junit] Running org.apache.commons.id.uuid.state.StateHelperTest [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.327 sec [junit] Running org.apache.commons.id.uuid.state.InMemoryStateImplTest [junit] Tests run: 5, Failures: 1, Errors: 0, Time elapsed: 0.319 sec [junit] [ERROR] TEST org.apache.commons.id.uuid.state.InMemoryStateImplTest FAILED [junit] Running org.apache.commons.id.uuid.UUIDTest [junit] Tests run: 17, Failures: 0, Errors: 0, Time elapsed: 0.278 sec [junit] Running org.apache.commons.id.uuid.NodeManagerImplTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.427 sec [junit] Running org.apache.commons.id.uuid.task.UUIDTaskTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.494 sec [junit] Running org.apache.commons.id.uuid.clock.ThreadClockImplTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.26 sec [junit] Running org.apache.commons.id.uuid.clock.SystemClockImplTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.254 sec [junit] Running org.apache.commons.id.serial.AlphanumericGeneratorTest [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.265 sec [junit] Running org.apache.commons.id.serial.LongGeneratorTest [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.259 sec [junit] Running org.apache.commons.id.serial.PrefixedNumericGeneratorTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.242 sec [junit] Running org.apache.commons.id.serial.NumericGeneratorTest [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.258 sec [junit] Running org.apache.commons.id.serial.PrefixedLeftPaddedNumericGeneratorTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.255 sec [junit] Running org.apache.commons.id.serial.PrefixedAlphanumericGeneratorTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.253 sec [junit] Running org.apache.commons.id.serial.TimeBasedAlphanumericIdentifierGeneratorTest [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 0.744 sec [junit] Running org.apache.commons.id.CompositeIdentifierGeneratorTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.277 sec [junit] Running org.apache.commons.id.ConstantIdentifierGeneratorTest [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.275 sec BUILD FAILED File.. /home/gump/.maven/cache/maven-test-plugin-1.6.2/plugin.jelly Element... fail Line.. 181 Column 54 There were test failures. Total time: 23 seconds Finished at: Sun Mar 25 07:39:03 UTC 2012 - To subscribe to this information via
[GUMP@vmgump]: Project commons-vfs2-test (in module apache-commons) failed
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 gene...@gump.apache.org. Project commons-vfs2-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 52 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-vfs2-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-vfs2-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/vfs/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/vfs/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/vfs/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/vfs/core/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-vfs2-test/gump_work/build_apache-commons_commons-vfs2-test.html Work Name: build_apache-commons_commons-vfs2-test (Type: Build) Work ended in a state of : Failed Elapsed: 3 mins 4 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/vfs/gump_mvn_settings.xml package [Working Directory: /srv/gump/public/workspace/apache-commons/vfs] M2_HOME: /opt/maven2 - Tests in error: testDefaultInstance(org.apache.commons.vfs2.test.FileSystemManagerFactoryTestCase): Could not create a file system manager of class org.apache.commons.vfs2.impl.StandardFileSystemManager. org.apache.commons.vfs2.PatternFileSelectorTest: Could not create a file system manager of class org.apache.commons.vfs2.impl.StandardFileSystemManager. org.apache.commons.vfs2.FileTypeSelectorTest: Could not create a file system manager of class org.apache.commons.vfs2.impl.StandardFileSystemManager. org.apache.commons.vfs2.FileIteratorTest: Could not create a file system manager of class org.apache.commons.vfs2.impl.StandardFileSystemManager. junit.framework.TestSuite@c75e4fc(org.apache.commons.vfs2.test.CacheTestSuite): org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V junit.framework.TestSuite@7e78fc6(org.apache.commons.vfs2.test.CacheTestSuite): org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V testDelegatingBad(org.apache.commons.vfs2.util.DelegatingFileSystemOptionsBuilderTest): org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V testConfiguration(org.apache.commons.vfs2.util.DelegatingFileSystemOptionsBuilderTest): org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V testDelegatingGood(org.apache.commons.vfs2.util.DelegatingFileSystemOptionsBuilderTest): org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V junit.framework.TestSuite@379e8f17(org.apache.commons.vfs2.test.ProviderTestSuite): org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V junit.framework.TestSuite@39385660(org.apache.commons.vfs2.test.ProviderTestSuite): org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V junit.framework.TestSuite@44a613f8(org.apache.commons.vfs2.test.ProviderTestSuite): org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V junit.framework.TestSuite@40589e56(org.apache.commons.vfs2.test.ProviderTestSuite): org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V junit.framework.TestSuite@6c69d02b(org.apache.commons.vfs2.provider.ftp.test.FtpProviderTestCase$1): org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V junit.framework.TestSuite@7c0b6548(org.apache.commons.vfs2.test.ProviderTestSuite): org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V org.apache.commons.vfs2.provider.test.FileObjectSortTestCase: Could not create a file system manager of class org.apache.commons.vfs2.impl.StandardFileSystemManager.
Re: [graph][discuss] reintegrating branch in trunk
Hi Simone, While rearranging stuff to prepare the merge, I noticed that the NamedExportSelector disappeared in favor of specifying the graph name inside the usingXXXFormat() method. I honestly think that in that way it lost part of the expressiveness - even if it is less verbose. I am in favor of having it reintegrated before merging back, with his pros and cons - WDYT? so if I get it right, now we have: export( actual ).usingDotNotation( my graph ) .withVertexLabels( new VertexLabelMapper() ) .withEdgeWeights( new EdgeWeightMapper() ) .withEdgeLabels( new EdgeLabelMapper() ) .to( System.out ); which becomes something like: export( actual ).usingDotNotation().withName( my graph ) .withVertexLabels( new VertexLabelMapper() ) .withEdgeWeights( new EdgeWeightMapper() ) .withEdgeLabels( new EdgeLabelMapper() ) .to( System.out ); and in both cases the name is not required. If the above is correct I am quite neutral about the matter... how do you call it, a +0? :) PS. spoiler: I am thinking about importers now -- it is not trivial to get them right with this new model implementation. I'll start a discussion about that when we are done with the merge! Ciao, Claudio best and TIA, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, Mar 23, 2012 at 4:16 PM, Simone Tripodi simonetrip...@apache.org wrote: Yup I am aware that they are not completed, anyway I would like to encourage their development on /trunk because: * new algorithms can be implemented using new APIs (and I have an idea about a new one) * code is still in sandbox, no risk to break anything So I'll merge last Thomas' commit in trunk, then merging back to /trunk. All the best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, Mar 23, 2012 at 3:28 PM, Claudio Squarcella squar...@dia.uniroma3.it wrote: Hi, we could merge the branch and open some issues on Jira to track the exporter problems, so people can contribute to fix them. +1. Note that the exporters are not complete yet, and there are still interesting architectural decisions left unanswered. Let's go for it! Claudio -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [CSV] trimming spaces - are both leading/trailing required?
sounds reasonable indeed, let users chose the preferred behavior. FWIW, +1 as well :) -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sat, Mar 24, 2012 at 10:27 PM, Emmanuel Bourg ebo...@apache.org wrote: +1 for a single parameter controlling the trimming of the values (quoted or not). Emmanuel Bourg Le 23/03/2012 12:36, sebb a écrit : Do we really need to support independent leading/trailing spaces? I've been unable to find any reference to formats that require this. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph][discuss] reintegrating branch in trunk
Hi Claud.io, which becomes something like: export( actual ).usingDotNotation().withName( my graph ) .withVertexLabels( new VertexLabelMapper() ) .withEdgeWeights( new EdgeWeightMapper() ) .withEdgeLabels( new EdgeLabelMapper() ) .to( System.out ); almost, the NamedExportSelector was set before the format selection - and the chained APIs allowed skipping it. I'm going to restore it in the branch and try to hurry on moving branches so we can move discussions forward. Thanks for the hard work! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph][discuss] reintegrating branch in trunk
branches reintegrated, have a good work! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sun, Mar 25, 2012 at 1:22 PM, Simone Tripodi simonetrip...@apache.org wrote: Hi Claud.io, which becomes something like: export( actual ).usingDotNotation().withName( my graph ) .withVertexLabels( new VertexLabelMapper() ) .withEdgeWeights( new EdgeWeightMapper() ) .withEdgeLabels( new EdgeLabelMapper() ) .to( System.out ); almost, the NamedExportSelector was set before the format selection - and the chained APIs allowed skipping it. I'm going to restore it in the branch and try to hurry on moving branches so we can move discussions forward. Thanks for the hard work! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[graph] graph importers
Hi all, the implementation of importers for [graph] requires a bit of attention, in particular with the new model where * there are no explicit markers for Vertex and Edge, * all properties of Vertices and Edges are now specified with generic Mappers. Writing and extending exporters is fine: we first specify the graph, then its properties one after the other in a fluent chain. The exporter simply forgets about the types of Vertex/Edge and serializes the whole input. Importing back a graph from an input source, however, is not as simple because: * standard file formats give us no indication about Vertex/Edge types; * serialized graphs come with a number of properties, some of which we know and sometimes need for graph processing (e.g. labels and weights), while some others are not (yet?) recognized in the code; * the return type of any importer should account for both the graph itself and all the properties. As a first step, these are my suggestions for the design: * we need at least default, empty implementations for Vertex and Edge; together with that, we could do some black magic to allow the user to specify what types should be used to map imported Vertices/Edges to actual classes. * we need a structure to host both the imported graph and properties. And it should be easy for the user to query such a structure for specific graph properties, i.e. we need to isolate properties that we recognize and use in our algorithms (e.g. weights). Other properties could be either ignored or imported with a reference to their name in the input format. One way could be to explicitly ask the user to list all the properties that he expects from the input graph, raising exceptions if they are not found. Something like: * importGraph().asGraphML( graph1.gml ).withEdgeWeights().withVertexLabels(); // only two properties loaded and explicitly identified * importGraph().asGraphML( graph2.gml ).withAllProperties(); // all properties are loaded, none is explicitly recognized ...wow that was long. What do you [graph]ers think? :) Ciao, Claudio -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[math]:Complex types
Interesting article about value types in the JVM with relevance to better support for Complex numbers (something I've long wished for) https://blogs.oracle.com/jrose/entry/value_types_in_the_vm Perhaps there is a role for the Commons Math project in item 2 of his section More Work Bruce - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: svn commit: r1305050 - in /commons/sandbox/graph/trunk/src/main/java/org/apache/commons/graph/spanning: DefaultSpanningTreeSourceSelector.java ReverseDeleteGraph.java
Great, I like it!
just a minor observation:
+ for ( int i = 0; i sortedEdge.size(); i++ )
{
- WE we = iterator.next();
- iterator.remove();
+ WE we = sortedEdge.poll();
do we really need to cycle guarding an accumulator? I'd replace it with:
while ( !sortedEdge.isEmpty() )
{
WE we = sortedEdge.poll();
}
best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph] graph importers
Hi Claud.io I honestly felt I little lost - code would speak better than thousands of words, what about branching once again and make a concrete proposal? ;) Looking forward to read about it! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sun, Mar 25, 2012 at 3:20 PM, Claudio Squarcella squar...@dia.uniroma3.it wrote: Hi all, the implementation of importers for [graph] requires a bit of attention, in particular with the new model where * there are no explicit markers for Vertex and Edge, * all properties of Vertices and Edges are now specified with generic Mappers. Writing and extending exporters is fine: we first specify the graph, then its properties one after the other in a fluent chain. The exporter simply forgets about the types of Vertex/Edge and serializes the whole input. Importing back a graph from an input source, however, is not as simple because: * standard file formats give us no indication about Vertex/Edge types; * serialized graphs come with a number of properties, some of which we know and sometimes need for graph processing (e.g. labels and weights), while some others are not (yet?) recognized in the code; * the return type of any importer should account for both the graph itself and all the properties. As a first step, these are my suggestions for the design: * we need at least default, empty implementations for Vertex and Edge; together with that, we could do some black magic to allow the user to specify what types should be used to map imported Vertices/Edges to actual classes. * we need a structure to host both the imported graph and properties. And it should be easy for the user to query such a structure for specific graph properties, i.e. we need to isolate properties that we recognize and use in our algorithms (e.g. weights). Other properties could be either ignored or imported with a reference to their name in the input format. One way could be to explicitly ask the user to list all the properties that he expects from the input graph, raising exceptions if they are not found. Something like: * importGraph().asGraphML( graph1.gml ).withEdgeWeights().withVertexLabels(); // only two properties loaded and explicitly identified * importGraph().asGraphML( graph2.gml ).withAllProperties(); // all properties are loaded, none is explicitly recognized ...wow that was long. What do you [graph]ers think? :) Ciao, Claudio -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: svn commit: r1305050 - in /commons/sandbox/graph/trunk/src/main/java/org/apache/commons/graph/spanning: DefaultSpanningTreeSourceSelector.java ReverseDeleteGraph.java
I just modified it, see r1305065
best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Sun, Mar 25, 2012 at 4:46 PM, Simone Tripodi
simonetrip...@apache.org wrote:
Great, I like it!
just a minor observation:
+ for ( int i = 0; i sortedEdge.size(); i++ )
{
- WE we = iterator.next();
- iterator.remove();
+ WE we = sortedEdge.poll();
do we really need to cycle guarding an accumulator? I'd replace it with:
while ( !sortedEdge.isEmpty() )
{
WE we = sortedEdge.poll();
}
best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph] graph importers
Hi, On 25/03/2012 17:33, Simone Tripodi wrote: Hi Claud.io I honestly felt I little lost - code would speak better than thousands of words, what about branching once again and make a concrete proposal? ;) Sure I'll open a branch for that. But first I would like to validate my thoughts (at least partially), that is why I'm writing poems for now :) An example: I'm very far from understanding how to exactly model the return type for importers. It should give access to both the graph and its properties, with particular emphasis on the ones that are relevant in [graph] like edge weights, vertex labels, etc. Any take on that? Cheers, Claudio Looking forward to read about it! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sun, Mar 25, 2012 at 3:20 PM, Claudio Squarcella squar...@dia.uniroma3.it wrote: Hi all, the implementation of importers for [graph] requires a bit of attention, in particular with the new model where * there are no explicit markers for Vertex and Edge, * all properties of Vertices and Edges are now specified with generic Mappers. Writing and extending exporters is fine: we first specify the graph, then its properties one after the other in a fluent chain. The exporter simply forgets about the types of Vertex/Edge and serializes the whole input. Importing back a graph from an input source, however, is not as simple because: * standard file formats give us no indication about Vertex/Edge types; * serialized graphs come with a number of properties, some of which we know and sometimes need for graph processing (e.g. labels and weights), while some others are not (yet?) recognized in the code; * the return type of any importer should account for both the graph itself and all the properties. As a first step, these are my suggestions for the design: * we need at least default, empty implementations for Vertex and Edge; together with that, we could do some black magic to allow the user to specify what types should be used to map imported Vertices/Edges to actual classes. * we need a structure to host both the imported graph and properties. And it should be easy for the user to query such a structure for specific graph properties, i.e. we need to isolate properties that we recognize and use in our algorithms (e.g. weights). Other properties could be either ignored or imported with a reference to their name in the input format. One way could be to explicitly ask the user to list all the properties that he expects from the input graph, raising exceptions if they are not found. Something like: * importGraph().asGraphML( graph1.gml ).withEdgeWeights().withVertexLabels(); // only two properties loaded and explicitly identified * importGraph().asGraphML( graph2.gml ).withAllProperties(); // all properties are loaded, none is explicitly recognized ...wow that was long. What do you [graph]ers think? :) Ciao, Claudio -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[graph][discuss] possible room for improvement for Visit handler APIs
Hi Graphers, I was trying to code the ELO algorithm using a BSF algo and got in trouble with the boolean return value of the visit handler methods - I think that we could improve it a little, adopting a similar approach of the AsyncHttpClient's AsyncHandler[1]: *maybe* having those methods that return a kind of STATE[2] enumeration would make APIs a little more intuitive. WDYT? TIA, -Simo [1] http://sonatype.github.com/async-http-client/request.html [2] http://sonatype.github.com/async-http-client/apidocs/reference/com/ning/http/client/AsyncHandler.STATE.html http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph][discuss] possible room for improvement for Visit handler APIs
Hi Simone, On 25/03/2012 22:46, Simone Tripodi wrote: Hi Graphers, I was trying to code the ELO algorithm using a BSF algo and got in trouble with the boolean return value of the visit handler methods - I think that we could improve it a little, adopting a similar approach of the AsyncHttpClient's AsyncHandler[1]: *maybe* having those methods that return a kind of STATE[2] enumeration would make APIs a little more intuitive. WDYT? if I get it right you are saying that two values (true/false) are too limiting for some of the current methods. Do you have a specific example, to get a clearer idea of the improvement? Thanks, Claudio TIA, -Simo [1] http://sonatype.github.com/async-http-client/request.html [2] http://sonatype.github.com/async-http-client/apidocs/reference/com/ning/http/client/AsyncHandler.STATE.html http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph][discuss] possible room for improvement for Visit handler APIs
if I get it right you are saying that two values (true/false) are too limiting for some of the current methods. Do you have a specific example, to get a clearer idea of the improvement? nope, I am saying that the boolean flag is less intuitive - I had to take a (short, of course) while to realize the meaning, if returning `true` meant `stop it` or `continue it`. Yes, maybe I am already sleeping and that yesterday's TZ switch doesn't help, but if it happened to someone with hands on [graph], I wonder if that could happen to users as well. My proposal is switching to a more expressive values, kind of VisitState.(ABORT|CONTINUE) enumeration that is free of any misunderstanding. Thoughts? best and thanks, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph][discuss] possible room for improvement for Visit handler APIs
Hi, My proposal is switching to a more expressive values, kind of VisitState.(ABORT|CONTINUE) enumeration that is free of any misunderstanding. Thoughts? ok so something like: * if ( handler.finishEdge( prevHead, e, v ).equals( VisitState.ABORT ) ) .. Looks good to me, +1 :) Ciao, Claudio best and thanks, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph][discuss] possible room for improvement for Visit handler APIs
* if ( handler.finishEdge( prevHead, e, v ).equals( VisitState.ABORT ) ) .. even better: VisitState.ABORT == handler.finishEdge( prevHead, e, v ) Looks good to me, +1 :) great, I am going to change it - then sleeping to cheat the new TZ :P best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sun, Mar 25, 2012 at 11:15 PM, Claudio Squarcella squar...@dia.uniroma3.it wrote: Hi, My proposal is switching to a more expressive values, kind of VisitState.(ABORT|CONTINUE) enumeration that is free of any misunderstanding. Thoughts? ok so something like: Ciao, Claudio best and thanks, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph][discuss] possible room for improvement for Visit handler APIs
just had an idea of a possible new state: SKIP,that would mean skipping the children/subtrees... thoughts? :P -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sun, Mar 25, 2012 at 11:22 PM, Simone Tripodi simonetrip...@apache.org wrote: * if ( handler.finishEdge( prevHead, e, v ).equals( VisitState.ABORT ) ) .. even better: VisitState.ABORT == handler.finishEdge( prevHead, e, v ) Looks good to me, +1 :) great, I am going to change it - then sleeping to cheat the new TZ :P best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sun, Mar 25, 2012 at 11:15 PM, Claudio Squarcella squar...@dia.uniroma3.it wrote: Hi, My proposal is switching to a more expressive values, kind of VisitState.(ABORT|CONTINUE) enumeration that is free of any misunderstanding. Thoughts? ok so something like: Ciao, Claudio best and thanks, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph][discuss] possible room for improvement for Visit handler APIs
Hi, On 25/03/2012 23:27, Simone Tripodi wrote: just had an idea of a possible new state: SKIP,that would mean skipping the children/subtrees... thoughts? :P +1. Of course we still need to document the whole thing in the javadoc (as we did already with boolean values), but the readability of the code is a clear advantage. Thanks, Claudio -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph][discuss] possible room for improvement for Visit handler APIs
just filled SANDBOX-416 and committed the org.apache.commons.graph.visit.VisitState enum, now I am too sleepy to continue - feel free to finalize it if you want/can/have spare time/... all the best and thanks for discussing, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sun, Mar 25, 2012 at 11:36 PM, Claudio Squarcella squar...@dia.uniroma3.it wrote: Hi, On 25/03/2012 23:27, Simone Tripodi wrote: just had an idea of a possible new state: SKIP,that would mean skipping the children/subtrees... thoughts? :P +1. Of course we still need to document the whole thing in the javadoc (as we did already with boolean values), but the readability of the code is a clear advantage. Thanks, Claudio -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [graph][discuss] possible room for improvement for Visit handler APIs
Hi, On 25/03/2012 23:45, Simone Tripodi wrote: just filled SANDBOX-416 and committed the org.apache.commons.graph.visit.VisitState enum, now I am too sleepy to continue - feel free to finalize it if you want/can/have spare time/... I did that, see the comment on SANDBOX-416 :) Ciao, Claudio all the best and thanks for discussing, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sun, Mar 25, 2012 at 11:36 PM, Claudio Squarcella squar...@dia.uniroma3.it wrote: Hi, On 25/03/2012 23:27, Simone Tripodi wrote: just had an idea of a possible new state: SKIP,that would mean skipping the children/subtrees... thoughts? :P +1. Of course we still need to document the whole thing in the javadoc (as we did already with boolean values), but the readability of the code is a clear advantage. Thanks, Claudio -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://twitter.com/hyperboreans http://claudio.squarcella.com/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GUMP@vmgump]: Project commons-digester3 (in module apache-commons) failed
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 gene...@gump.apache.org.
Project commons-digester3 has an issue affecting its community integration.
This issue affects 2 projects,
and has been outstanding for 86 runs.
The current state of this project is 'Failed', with reason 'Missing Build
Outputs'.
For reference only, the following projects are affected by this:
- commons-digester3 : XML to Java Object Configuration
- commons-digester3-test : Apache Commons
Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole jar output [commons-digester3-*[0-9T].jar] identifier set to
project name
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml
-DEBUG- Maven POM in:
/srv/gump/public/workspace/apache-commons/digester/pom.xml
-INFO- Failed with reason missing build outputs
-ERROR- Missing Output:
/srv/gump/public/workspace/apache-commons/digester/target/commons-digester3-*[0-9T].jar
-ERROR- See Directory Listing Work for Missing Outputs
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/gump_work/build_apache-commons_commons-digester3.html
Work Name: build_apache-commons_commons-digester3 (Type: Build)
Work ended in a state of : Success
Elapsed: 1 min 32 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml
package
[Working Directory: /srv/gump/public/workspace/apache-commons/digester]
M2_HOME: /opt/maven2
-
Downloading:
http://localhost:8192/maven2/org/apache/maven/maven-monitor/2.2.1/maven-monitor-2.2.1.pom
Downloading:
http://localhost:8192/maven2/org/apache/maven/wagon/wagon-ssh/1.0-beta-6/wagon-ssh-1.0-beta-6.pom
Downloading:
http://localhost:8192/maven2/org/codehaus/plexus/plexus-archiver/1.1/plexus-archiver-1.1.pom
Downloading:
http://localhost:8192/maven2/org/apache/maven/shared/maven-repository-builder/1.0-alpha-2/maven-repository-builder-1.0-alpha-2.pom
Downloading:
http://localhost:8192/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.0-alpha-1/maven-common-artifact-filters-1.0-alpha-1.pom
Downloading:
http://localhost:8192/maven2/org/apache/maven/shared/maven-shared-components/6/maven-shared-components-6.pom
Downloading:
http://localhost:8192/maven2/org/codehaus/plexus/plexus-archiver/1.1/plexus-archiver-1.1.jar
Downloading:
http://localhost:8192/maven2/org/apache/maven/shared/maven-repository-builder/1.0-alpha-2/maven-repository-builder-1.0-alpha-2.jar
[INFO] [assembly:single {execution: default}]
[INFO] Reading assembly descriptor:
/srv/gump/public/workspace/apache-commons/digester/dist/src/main/assembly/bin.xml
[INFO] Reading assembly descriptor:
/srv/gump/public/workspace/apache-commons/digester/dist/src/main/assembly/src.xml
[INFO] Building tar :
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-bin.tar.gz
[INFO] Building zip:
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-bin.zip
[INFO] Building tar :
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-src.tar.gz
[INFO] Building zip:
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-src.zip
[INFO]
[INFO]
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Commons Digester ... SUCCESS [10.624s]
[INFO] Apache Commons Digester :: Core ... SUCCESS [28.337s]
[INFO] Apache Commons Digester :: Annotations Processor .. SUCCESS [2.259s]
[INFO] Commons Digester :: Examples .. SUCCESS [0.607s]
[INFO] Apache Commons Digester :: Examples :: Annotations :: Atom SUCCESS
[3.187s]
[INFO] Apache Commons Digester :: Examples :: API :: Address Book SUCCESS
[1.939s]
[INFO] Apache Commons Digester :: Examples :: API :: Catalog . SUCCESS [1.632s]
[INFO] Apache Commons Digester :: Examples :: API :: DB Insert SUCCESS [1.912s]
[INFO] Apache Commons Digester :: Examples :: API :: Document Markup SUCCESS
[1.781s]
[INFO] Apache Commons Digester :: Examples :: EDSL :: Atom ... SUCCESS [1.886s]
[INFO] Apache Commons Digester :: Examples :: Plugins :: Pipeline SUCCESS
[1.547s]
[INFO] Apache Commons Digester :: Examples
[GUMP@vmgump]: Project commons-graph (in module commons-sandbox) failed
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 gene...@gump.apache.org. Project commons-graph has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 19 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-graph : Apache commons sandbox Full details are available at: http://vmgump.apache.org/gump/public/commons-sandbox/commons-graph/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole jar output [commons-graph-*[0-9T].jar] identifier set to project name -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/commons-sandbox/graph/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-sandbox/graph/pom.xml -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-sandbox/commons-graph/gump_work/build_commons-sandbox_commons-graph.html Work Name: build_commons-sandbox_commons-graph (Type: Build) Work ended in a state of : Failed Elapsed: 17 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/commons-sandbox/graph/gump_mvn_settings.xml install [Working Directory: /srv/gump/public/workspace/commons-sandbox/graph] M2_HOME: /opt/maven2 - [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/CommonsGraph.java:[179,61] withConnections(org.apache.commons.graph.builder.GraphConnectionjava.lang.Object,java.lang.Object) in org.apache.commons.graph.builder.LinkedConnectionBuilderjava.lang.Object,java.lang.Object,org.apache.commons.graph.model.UndirectedMutableGraphV,E cannot be applied to (org.apache.commons.graph.builder.GraphConnectionV,E) [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[75,43] cannot find symbol symbol : method applyingDepthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandlerV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE,W) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelectorjava.lang.Object,java.lang.Object,org.apache.commons.graph.DirectedGraphV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[82,47] cannot find symbol symbol : method applyingDepthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandlerV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE,W) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelectorjava.lang.Object,java.lang.Object,org.apache.commons.graph.DirectedGraphV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[103,43] cannot find symbol symbol : method applyingBreadthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandlerV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE,W) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelectorjava.lang.Object,java.lang.Object,org.apache.commons.graph.DirectedGraphV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[110,47] cannot find symbol symbol : method applyingBreadthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandlerV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE,W) location: interface org.apache.commons.graph.visit.VisitAlgorithmsSelectorjava.lang.Object,java.lang.Object,org.apache.commons.graph.DirectedGraphV,org.apache.commons.graph.flow.DefaultMaxFlowAlgorithmSelector.EdgeWrapperWE [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/spanning/DefaultSpanningTreeSourceSelector.java:[109,20] W,MwhereEdgesHaveWeights(M) in org.apache.commons.graph.shortestpath.PathWeightedEdgesBuilderjava.lang.Object,java.lang.Object cannot be applied to (org.apache.commons.graph.MapperWE,W) [ERROR] /srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/connectivity/DefaultConnectivityAlgorithmsSelector.java:[68,64] cannot find symbol symbol
[GUMP@vmgump]: Project commons-collections4-testframework (in module apache-commons) failed
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 gene...@gump.apache.org. Project commons-collections4-testframework has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 25 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - commons-collections4-testframework : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-collections4-testframework/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole jar output [commons-collections-testframework-*[0-9T].jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /srv/gump/public/workspace/apache-commons/collections/target/commons-collections-testframework-*[0-9T].jar -ERROR- See Directory Listing Work for Missing Outputs -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-collections4-testframework/rss.xml - Atom: http://vmgump.apache.org/gump/public/apache-commons/commons-collections4-testframework/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 1226032012, vmgump.apache.org:vmgump:1226032012 Gump E-mail Identifier (unique within run) #20. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GUMP@vmgump]: Project commons-scxml-test (in module apache-commons) failed
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 gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 67 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-scxml-test : Apache Commons
Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-WARNING- Overriding Maven settings:
[/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml]
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/scxml/pom.xml
-INFO- Project Reports in:
/srv/gump/public/workspace/apache-commons/scxml/target/surefire-reports
The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/gump_work/build_apache-commons_commons-scxml-test.html
Work Name: build_apache-commons_commons-scxml-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 19 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -Dsimplelog.defaultlog=info
--settings
/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml test
[Working Directory: /srv/gump/public/workspace/apache-commons/scxml]
M2_HOME: /opt/maven2
-
[INFO] SimpleSCXMLListener - /s2/s2.1/e1.2
[INFO] SimpleSCXMLListener - /s2/s2.1/e1.2
[INFO] SimpleSCXMLListener - /s2/s2.1
[INFO] SimpleSCXMLListener - /s2
[INFO] SimpleSCXMLListener - transition (event = s2.1.done, cond = null, from =
/s2, to = /s3)
[INFO] SimpleSCXMLListener - /s3
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.14 sec
Running org.apache.commons.scxml.issues.Issue64Test
[INFO] SCXMLSemantics - null: Begin transition bug test ...
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SCXMLSemantics - null: somedata
[INFO] SCXMLSemantics - null: *somedata
[INFO] SimpleSCXMLListener - transition (event = show.bug, cond = null, from =
/tranbug, to = /end)
[INFO] SimpleSCXMLListener - /end
[WARN] SCXMLParser - Ignoring element misplaced in namespace
http://www.w3.org/2005/07/scxml; at
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:30:21
and digester match scxml/datamodel/misplaced
[WARN] SCXMLParser - Ignoring element foo in namespace
http://www.w3.org/2005/07/scxml; at
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:36:19
and digester match scxml/state/onentry/foo
[WARN] SCXMLParser - Ignoring element bar in namespace
http://my.foo.example/; at
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:37:22
and digester match scxml/state/onentry/bar
[WARN] SCXMLParser - Ignoring element datamodel in namespace
http://www.w3.org/2005/07/scxml; at
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:41:21
and digester match scxml/state/transition/datamodel
[WARN] SCXMLParser - Ignoring element data in namespace
http://www.w3.org/2005/07/scxml; at
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:42:41
and digester match scxml/state/transition/datamodel/data
[WARN] SCXMLParser - Ignoring element baz in namespace
http://my.foo.example/; at
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:49:14
and digester match scxml/baz
[INFO] SCXMLSemantics - null: Begin transition bug test ...
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SCXMLSemantics - null: null
[WARN] SimpleErrorReporter - EXPRESSION_ERROR (eval(''*' + dummy'):null):
[INFO] SimpleSCXMLListener - transition (event = show.bug, cond = null, from =
/tranbug, to = /end)
[INFO] SimpleSCXMLListener - /end
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec
Results :
Failed tests:
testCustomActionCallbacks(org.apache.commons.scxml.model.CustomActionTest)
Tests run: 229, Failures: 1, Errors: 0, Skipped: 0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
