[g...@vmgump]: Project commons-javaflow (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-javaflow has an issue affecting its community integration.
This issue affects 1 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:
- commons-javaflow : Commons Javaflow
Full details are available at:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-javaflow/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-javaflow-*[0-9T].jar] identifier set to
project name
-DEBUG- (Gump generated) Maven2 Settings in:
/srv/gump/public/workspace/commons-sandbox/javaflow/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/commons-sandbox/javaflow/pom.xml
-INFO- Project Reports in:
/srv/gump/public/workspace/commons-sandbox/javaflow/target/surefire-reports
-WARNING- No directory
[/srv/gump/public/workspace/commons-sandbox/javaflow/target/surefire-reports]
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-javaflow/gump_work/build_commons-sandbox_commons-javaflow.html
Work Name: build_commons-sandbox_commons-javaflow (Type: Build)
Work ended in a state of : Failed
Elapsed: 19 secs
Command Line: mvn --batch-mode --settings
/srv/gump/public/workspace/commons-sandbox/javaflow/gump_mvn_settings.xml
package
[Working Directory: /srv/gump/public/workspace/commons-sandbox/javaflow]
-
Downloading:
http://localhost:8192/maven2/asm/asm-analysis/3.2/asm-analysis-3.2.jar
17K downloaded (asm-analysis-3.2.jar)
Downloading: http://localhost:8192/maven2/asm/asm-util/3.2/asm-util-3.2.jar
34K downloaded (asm-util-3.2.jar)
[INFO] [antrun:run {execution: javadoc.resources}]
[INFO] Executing tasks
[copy] Copying 2 files to
/srv/gump/public/workspace/commons-sandbox/javaflow/target/apidocs/META-INF
[INFO] Executed tasks
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] Copying 2 resources to META-INF
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 35 source files to
/srv/gump/public/workspace/commons-sandbox/javaflow/target/classes
[INFO] [bundle:manifest {execution: bundle-manifest}]
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/srv/gump/public/workspace/commons-sandbox/javaflow/src/test/resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 23 source files to
/srv/gump/public/workspace/commons-sandbox/javaflow/target/test-classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/srv/gump/public/workspace/commons-sandbox/javaflow/src/test/java/org/apache/commons/javaflow/AsmTestSuite.java:[73,13]
addTestSuite(java.lang.Class) in
junit.framework.TestSuite cannot be applied to (java.lang.Class)
[ERROR]
/srv/gump/public/workspace/commons-sandbox/javaflow/src/test/java/org/apache/commons/javaflow/AsmTestSuite.java:[74,13]
addTestSuite(java.lang.Class) in
junit.framework.TestSuite cannot be applied to (java.lang.Class)
[INFO] 2 errors
[INFO] -
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/srv/gump/public/workspace/commons-sandbox/javaflow/src/test/java/org/apache/commons/javaflow/AsmTestSuite.java:[73,13]
addTestSuite(java.lang.Class) in
junit.framework.TestSuite cannot be applied to (java.lang.Class)
/srv/gump/public/workspace/commons-sandbox/javaflow/src/test/java/org/apache/commons/javaflow/AsmTestSuite.java:[74,13]
addTestSuite(java.lang.Class) in
junit.framework.TestSuite cannot be applied to (java.lang.Class)
[INFO]
[INFO] For more i
[g...@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 45 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 Maven2 settings: [/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml] -DEBUG- (Gump generated) Maven2 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: 10 secs Command Line: 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] - 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.012 sec Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.038 sec Running org.apache.commons.proxy.interceptor.filter.TestPatternFilter Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec Running org.apache.commons.proxy.interceptor.TestInterceptorChain Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec Running org.apache.commons.proxy.invoker.TestNullInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 sec Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec Running org.apache.commons.proxy.exception.TestDelegateProviderException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.proxy.invoker.TestChainInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 sec Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.182 sec Running org.apache.commons.proxy.exception.TestProxyFactoryException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 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.024 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: 9 seconds [INFO] Finished at: Fri Sep 10 05:49:31 UTC 2010 [INFO] Final Memory: 39M/93M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/rss.xml - Atom: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/at
[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 45 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 Maven2 settings: [/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml] -DEBUG- (Gump generated) Maven2 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: mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/scxml] - --- T E S T S --- Running org.apache.commons.scxml.invoke.InvokeTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.732 sec Running org.apache.commons.scxml.test.TestingTestSuite Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running org.apache.commons.scxml.env.EnvTestSuite Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.202 sec Running org.apache.commons.scxml.SCXMLTestSuite Tests run: 71, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.083 sec <<< FAILURE! Running org.apache.commons.scxml.issues.IssuesTestSuite Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.363 sec Running org.apache.commons.scxml.model.ModelTestSuite Tests run: 78, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.371 sec <<< FAILURE! Running org.apache.commons.scxml.env.faces.EnvFacesTestSuite Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running org.apache.commons.scxml.semantics.SemanticsTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.scxml.env.jsp.EnvJspTestSuite Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.037 sec Running org.apache.commons.scxml.env.jexl.EnvJexlTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.041 sec Running org.apache.commons.scxml.env.servlet.EnvServletTestSuite Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.scxml.io.IOTestSuite Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.636 sec Results : Failed tests: testNamespacePrefixedXPathsEL(org.apache.commons.scxml.NamespacePrefixedXPathsTest) testDatamodelSimultaneousJsp(org.apache.commons.scxml.model.DatamodelTest) Tests run: 228, Failures: 2, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /srv/gump/public/workspace/apache-commons/scxml/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 18 seconds [INFO] Finished at: Fri Sep 10 05:08:33 UTC 2010 [INFO] Final Memory: 40M/97M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/rss.xml - Atom: http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 1710092010, vmgump.apache.org:vmgump:1710092010 Gump E-mail Identifier (unique within run) #16. -- Apache Gump http://gump.apache.org/ [Instan
[GUMP@vmgump]: Project commons-io-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-io-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-io-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-io-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven2 settings: [/srv/gump/public/workspace/apache-commons/io/gump_mvn_settings.xml] -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/apache-commons/io/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/io/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/io/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-io-test/gump_work/build_apache-commons_commons-io-test.html Work Name: build_apache-commons_commons-io-test (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 54 secs Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/io/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/io] - Running org.apache.commons.io.output.StringBuilderWriterTest Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.09 sec Running org.apache.commons.io.comparator.ExtensionFileComparatorTest Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.095 sec Running org.apache.commons.io.FileUtilsFileNewerTestCase Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.084 sec Running org.apache.commons.io.input.CountingInputStreamTest Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.112 sec Running org.apache.commons.io.input.ProxyReaderTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec Running org.apache.commons.io.output.NullWriterTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec Running org.apache.commons.io.output.TeeOutputStreamTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.069 sec Running org.apache.commons.io.comparator.SizeFileComparatorTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.098 sec Running org.apache.commons.io.FileUtilsListFilesTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.101 sec Running org.apache.commons.io.comparator.DirectoryFileComparatorTest Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.086 sec Running org.apache.commons.io.filefilter.AndFileFilterTestCase Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.071 sec Running org.apache.commons.io.TaggedIOExceptionTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec Running org.apache.commons.io.input.TaggedInputStreamTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.063 sec Running org.apache.commons.io.HexDumpTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.093 sec Running org.apache.commons.io.input.CloseShieldInputStreamTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec Results : Tests in error: Tests run: 645, 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/io/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 52 seconds [INFO] Finished at: Fri Sep 10 02:31:02 UTC 2010 [INFO] Final Memory: 38M/92M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-io-test/rss.xml - Atom: http://vmgump.apache.org/gump/public/apache-commons/commons-io-test/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 1710092010, vmgump.apache.org:vmgump:1710092010 Gump E-mail Ide
Re: [SANSELAN] Fixing test case Eclipse warnings
On 9 September 2010 20:56, Charles Matthew Chen wrote: > Sebb, please feel free to clean up warnings, etc. in Sanselan. > There's tons of code clean up that I'd like to do if I ever have time. OK, thanks. I've now fixed the more obvious warnings. There are still a lot of unthrown Exceptions, but as the remaining ones are part of the public API I did not remove them yet. We should either document them (which prevents the Eclipse warning) or remove them, e.g. when 1.0 is released. Most of the code is infested with tabs (I'll start getting rid of the ones in the test code first). > +1 to have more active committers on Sanselan. > > Charles Matthew > > > On Wed, Sep 8, 2010 at 1:48 PM, Matt Benson wrote: >> For my part, I should think the community would be glad for someone in >> addition to Charles to have his hands in sanselan. >> >> -Matt >> >> On Sep 8, 2010, at 11:37 AM, sebb wrote: >> >>> There are quite a few Eclipse warnings in the Sanselan test code. >>> >>> For example, test cases that declare impossible Exceptions. >>> Also potential null pointer exceptions that can be fixed either by: >>> - changing assertTrue(null != value) to assertNotNull(value) >>> - or by explicitly checking for null >>> >>> Any objections if I just fix these? >>> >>> Or should I create a JIRA with patches first? >>> >>> - >>> 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 > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [SANSELAN] Non-serializable ArrayLists
PS -- I'd be happy to take a stab at this. On 9/9/10 5:52 PM, Paul Szynol wrote: I found recently is that some getItems() calls return non-serializable ArrayLists, which, for my purposes, was a small handicap. Is there a native solution to this, does anyone know? If not, I wonder if this is something that may be worth adding? Best, Paul - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[SANSELAN] Non-serializable ArrayLists
I found recently is that some getItems() calls return non-serializable ArrayLists, which, for my purposes, was a small handicap. Is there a native solution to this, does anyone know? If not, I wonder if this is something that may be worth adding? Best, Paul - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [SANSELAN] Fixing test case Eclipse warnings
Sebb, please feel free to clean up warnings, etc. in Sanselan. There's tons of code clean up that I'd like to do if I ever have time. +1 to have more active committers on Sanselan. Charles Matthew On Wed, Sep 8, 2010 at 1:48 PM, Matt Benson wrote: > For my part, I should think the community would be glad for someone in > addition to Charles to have his hands in sanselan. > > -Matt > > On Sep 8, 2010, at 11:37 AM, sebb wrote: > >> There are quite a few Eclipse warnings in the Sanselan test code. >> >> For example, test cases that declare impossible Exceptions. >> Also potential null pointer exceptions that can be fixed either by: >> - changing assertTrue(null != value) to assertNotNull(value) >> - or by explicitly checking for null >> >> Any objections if I just fix these? >> >> Or should I create a JIRA with patches first? >> >> - >> 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
[continuum] BUILD FAILURE: Apache Commons - Commons IO - Default Maven 2 Build Definition
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=455&projectId=83 Build statistics: State: Failed Previous State: Ok Started at: Thu 9 Sep 2010 19:20:45 + Finished at: Thu 9 Sep 2010 19:24:19 + Total time: 3m 33s Build Trigger: Schedule Build Number: 3 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_20 Java home: /usr/lib/jvm/java-6-sun-1.6.0.20/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-24-server" arch: "amd64" Family: "unix" SCM Changes: Changed: sebb @ Thu 9 Sep 2010 18:33:19 + Comment: IO-215 Clarify that file modification failure is not reported Files changed: /commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java ( 995532 ) Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean install Arguments: --batch-mode Build Fresh: false Always Build: false Default Build Definition: true Schedule: COMMONS_SCHEDULE Profile Name: Maven 2.2.1 Description: Default Maven 2 Build Definition Test Summary: Tests: 645 Failures: 1 Errors: 0 Success Rate: 99 Total time: 75.57599 Test Failures: FilesystemObserverTestCase testFileCreate : junit.framework.AssertionFailedError junit.framework.AssertionFailedError: E[0 0 0 1 0 0]: No. of directories changed expected:<1> but was:<0> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:283) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:195) at org.apache.commons.io.monitor.FilesystemObserverTestCase.checkCollectionSizes(FilesystemObserverTestCase.java:426) at org.apache.commons.io.monitor.FilesystemObserverTestCase.testFileCreate(FilesystemObserverTestCase.java:205) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.Surefire.run(Surefire.java:109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1017) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.o
Re: [Digester] working toward a release
On 9 September 2010 19:54, Simone Tripodi wrote:
> Hi all guys,
> I'm trying to push an RC release, but the gpg plugin execution is
> blocked when signing arifacts :( Follow below my attempts:
>
> mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=\
> -Dgpg.passphrase=
> mvn release:prepare -DdryRun=true -Dgpg.passphrase= (the keyname
> is defined as preferred in the gpg.conf)
> mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the
> prompt)
>
> Do you have any idea why? Many thanks in advance,
> Simo
I use a profile in my settings.xml which defines the keyname, so I
don't have to remember the hex string.
One can also define gpg.homedir and gpg.executable (if required)
The password you can omit - it should be prompted for, but how depends
on whether you are using gpg1 or gpg2.
For testing gpg signing, you can use the new "test-deploy" profile.
Don't you need to use mvn deploy ?
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Mon, Sep 6, 2010 at 10:03 PM, Simone Tripodi
> wrote:
>> Hi Rahul,
>> don't worry I won't publish the site before the release; about the
>> Menu reorganization I like the b) too, it is much more coherent with
>> previous releases.
>> Thanks a lot, have a nice day,
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Mon, Sep 6, 2010 at 6:23 PM, Rahul Akolkar
>> wrote:
>>> On Mon, Sep 6, 2010 at 9:49 AM, Simone Tripodi
>>> wrote:
Hi all, Rahul,
what about the latest deployed website?
>>>
>>>
>>> Looks good overall, though I haven't taken a fine-toothed comb to it.
>>>
>>>
Can I proceed modifying the
homepage in order to propose a release?
>>>
>>>
>>> Sure, but please don't deploy it after those changes until the release
>>> is done. Before posting the vote, the site is previewed w/ the rc
>>> profile (-Prc) in the site-deploy command -- this will deploy the site
>>> to the pao/commons/builds area where the other artifacts for the vote
>>> will get posted as well.
>>>
>>> WRT the new additions to the LHS menu, currently we have (indentation
>>> implies nesting):
>>>
>>> Developers Guide (SVN latest)
>>> Core APIs
>>> Plugins
>>> Substitution
>>> XML Rules
>>> Annotations
>>> FAQ
>>>
>>> I see two options for the 2.1 release:
>>>
>>> (a) Use the above (but change SVN latest to 2.1)
>>>
>>> (b) Use the following:
>>>
>>> Release 2.1 (Current)
>>> Guide
>>> Core APIs
>>> Plugins
>>> Substitution
>>> XML Rules
>>> Annotations
>>> FAQ
>>> Javadoc
>>> Release Notes
>>>
>>> Release 2.0
>>> ... (current content for 2.0 menu)
>>>
>>>
>>> I think (b) will work better as it aligns with menu for previous
>>> releases -- note the FAQ indentation in (b) BTW as its different --
>>> WDYT?
>>>
>>> -Rahul
>>>
>>>
Thanks in advance, all the best,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Sep 5, 2010 at 12:46 AM, Rahul Akolkar
wrote:
> On Sat, Sep 4, 2010 at 3:11 PM, Simone Tripodi
> wrote:
>> Hi Rahul,
>> thanks a lot for your feedbacks, actions have been completed following
>> your suggestions.
>> my final 2 questions:
>> - I didn't find any reference on wiki about
>> ${commons.deployment.protocol}... can we have a private chat?
>
>
> Sure, though it helps to have things in the list archives for the next
> person in line, so the responses are best when archived :-)
>
> The deployment protocol bit is for wagon and defaults to scp (see
> parent pom). If you want to use some other (for example, scpexe with
> PuTTY), then it can be changed via an active profile in
> ~/.m2/settings.xml. If you've used the m2 release plugin before, you
> probably don't need to do anything new for Commons.
>
>
>> - Is it the case to migrate the group id to org.apache.commons?
>
>
> No, not for 2.1 (archives have this topic at length).
>
> -Rahul
>
>
>> Many thanks in advance, namaste
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.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
>
>
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Re: [Digester] working toward a release
Hi all guys,
I'm trying to push an RC release, but the gpg plugin execution is
blocked when signing arifacts :( Follow below my attempts:
mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=\
-Dgpg.passphrase=
mvn release:prepare -DdryRun=true -Dgpg.passphrase= (the keyname
is defined as preferred in the gpg.conf)
mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the prompt)
Do you have any idea why? Many thanks in advance,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Mon, Sep 6, 2010 at 10:03 PM, Simone Tripodi
wrote:
> Hi Rahul,
> don't worry I won't publish the site before the release; about the
> Menu reorganization I like the b) too, it is much more coherent with
> previous releases.
> Thanks a lot, have a nice day,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Mon, Sep 6, 2010 at 6:23 PM, Rahul Akolkar wrote:
>> On Mon, Sep 6, 2010 at 9:49 AM, Simone Tripodi
>> wrote:
>>> Hi all, Rahul,
>>> what about the latest deployed website?
>>
>>
>> Looks good overall, though I haven't taken a fine-toothed comb to it.
>>
>>
>>> Can I proceed modifying the
>>> homepage in order to propose a release?
>>
>>
>> Sure, but please don't deploy it after those changes until the release
>> is done. Before posting the vote, the site is previewed w/ the rc
>> profile (-Prc) in the site-deploy command -- this will deploy the site
>> to the pao/commons/builds area where the other artifacts for the vote
>> will get posted as well.
>>
>> WRT the new additions to the LHS menu, currently we have (indentation
>> implies nesting):
>>
>> Developers Guide (SVN latest)
>> Core APIs
>> Plugins
>> Substitution
>> XML Rules
>> Annotations
>> FAQ
>>
>> I see two options for the 2.1 release:
>>
>> (a) Use the above (but change SVN latest to 2.1)
>>
>> (b) Use the following:
>>
>> Release 2.1 (Current)
>> Guide
>> Core APIs
>> Plugins
>> Substitution
>> XML Rules
>> Annotations
>> FAQ
>> Javadoc
>> Release Notes
>>
>> Release 2.0
>> ... (current content for 2.0 menu)
>>
>>
>> I think (b) will work better as it aligns with menu for previous
>> releases -- note the FAQ indentation in (b) BTW as its different --
>> WDYT?
>>
>> -Rahul
>>
>>
>>> Thanks in advance, all the best,
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Sun, Sep 5, 2010 at 12:46 AM, Rahul Akolkar
>>> wrote:
On Sat, Sep 4, 2010 at 3:11 PM, Simone Tripodi
wrote:
> Hi Rahul,
> thanks a lot for your feedbacks, actions have been completed following
> your suggestions.
> my final 2 questions:
> - I didn't find any reference on wiki about
> ${commons.deployment.protocol}... can we have a private chat?
Sure, though it helps to have things in the list archives for the next
person in line, so the responses are best when archived :-)
The deployment protocol bit is for wagon and defaults to scp (see
parent pom). If you want to use some other (for example, scpexe with
PuTTY), then it can be changed via an active profile in
~/.m2/settings.xml. If you've used the m2 release plugin before, you
probably don't need to do anything new for Commons.
> - Is it the case to migrate the group id to org.apache.commons?
No, not for 2.1 (archives have this topic at length).
-Rahul
> Many thanks in advance, namaste
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.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
