Re: svn commit: r1085247 - /commons/proper/codec/trunk/src/site/xdoc/index.xml
On Thu, Mar 24, 2011 at 11:55 PM, sebb wrote: > On 25 March 2011 03:50, wrote: > > Author: ggregory > > Date: Fri Mar 25 03:50:47 2011 > > New Revision: 1085247 > > > > URL: http://svn.apache.org/viewvc?rev=1085247&view=rev > > Log: > > Use a "Apache Commons Codec (TM)" the first time Codec is mentioned. > > > > Modified: > >commons/proper/codec/trunk/src/site/xdoc/index.xml > > > > Modified: commons/proper/codec/trunk/src/site/xdoc/index.xml > > URL: > http://svn.apache.org/viewvc/commons/proper/codec/trunk/src/site/xdoc/index.xml?rev=1085247&r1=1085246&r2=1085247&view=diff > > > == > > --- commons/proper/codec/trunk/src/site/xdoc/index.xml (original) > > +++ commons/proper/codec/trunk/src/site/xdoc/index.xml Fri Mar 25 > 03:50:47 2011 > > @@ -24,7 +24,7 @@ limitations under the License. > > > > > > > > -Commons Codec provides implementations of common encoders and decoders > > +Apache Commons Codec (TM) provides implementations of common encoders > and decoders > > That should ideally be > > Apache Commons Codec (TM) software provides ... > Done. Thank you for checking. Gary > > Brand names should be used as adjectives, at least initally. > > > such as Base64, Hex, Phonetic and URLs. > > > > > > > > -Codec 1.4 requires Java 1.4 > > Codec 1.5 requires Java 1.4 > > +Codec 1.4 requires Java 1.4 > > > > > > See the > > > > > > > -- Thank you, Gary http://garygregory.wordpress.com/ http://garygregory.com/ http://people.apache.org/~ggregory/ http://twitter.com/GaryGregory
Re: svn commit: r1085247 - /commons/proper/codec/trunk/src/site/xdoc/index.xml
On 25 March 2011 03:50, wrote: > Author: ggregory > Date: Fri Mar 25 03:50:47 2011 > New Revision: 1085247 > > URL: http://svn.apache.org/viewvc?rev=1085247&view=rev > Log: > Use a "Apache Commons Codec (TM)" the first time Codec is mentioned. > > Modified: > commons/proper/codec/trunk/src/site/xdoc/index.xml > > Modified: commons/proper/codec/trunk/src/site/xdoc/index.xml > URL: > http://svn.apache.org/viewvc/commons/proper/codec/trunk/src/site/xdoc/index.xml?rev=1085247&r1=1085246&r2=1085247&view=diff > == > --- commons/proper/codec/trunk/src/site/xdoc/index.xml (original) > +++ commons/proper/codec/trunk/src/site/xdoc/index.xml Fri Mar 25 03:50:47 > 2011 > @@ -24,7 +24,7 @@ limitations under the License. > > > > -Commons Codec provides implementations of common encoders and decoders > +Apache Commons Codec (TM) provides implementations of common encoders and > decoders That should ideally be Apache Commons Codec (TM) software provides ... Brand names should be used as adjectives, at least initally. > such as Base64, Hex, Phonetic and URLs. > > > > -Codec 1.4 requires Java 1.4 > Codec 1.5 requires Java 1.4 > +Codec 1.4 requires Java 1.4 > > > See the > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Apache Commons Codec 1.5-RC1
On Thu, Mar 24, 2011 at 10:18 PM, sebb wrote: > On 25 March 2011 01:39, Gary Gregory wrote: > > [VOTE] Release Apache Commons Codec 1.5-RC1 > > > > Tag: > > > > > https://svn.apache.org/repos/asf/commons/proper/codec/tags/commons-codec-1.5-RC1 > > > > Site: > > > > http://people.apache.org/builds/commons/codec/1.5/RC1/site/index.html > > AIUI from the branding perspective: > > Ideally there should be a TM after the first use of Commons Codec, and > it should be used as an adjective, e.g. > > Apache Commons Coded tm software is ... > > but these are not blockers, and can be fixed later. > > > Binaries: > > > > https://repository.apache.org/content/repositories/orgapachecommons-041/ > > Cannot find the signing key in the KEYS file:. > http://www.apache.org/dist/commons/KEYS > > That must be fixed before release. > Thank you for the quick feedback. I had updated the KEYS file in https://svn.apache.org/repos/asf/commons/trunks-proper/ but not copied it to people.apache.org:/www/www.apache.org/dist/commons which I now see mentioned here http://commons.apache.org/releases/prepare.html I used: scp KEYS people.apache.org:/www/www.apache.org/dist/commons but I do not see this reflected on the web yet. A cat of /x1/www/ www.apache.org/content/dist/commons/KEYS shows me that my update is there. Otherwise seems OK > > [I deleted the .asc.md5 and .asc.sha1 files] > I thought Nexus did that for you when you promote a release? Gary > > > > > [ ] +1 release it > > [ ] +0 go ahead I don't care > > [ ] -1 no, do not release it because > > > > Thank you, > > Gary > > > > http://garygregory.wordpress.com/ > > http://garygregory.com/ > > http://people.apache.org/~ggregory/ > > http://twitter.com/GaryGregory > > >
Re: [VOTE] Release Apache Commons Codec 1.5-RC1
On 25 March 2011 01:39, Gary Gregory wrote: > [VOTE] Release Apache Commons Codec 1.5-RC1 > > Tag: > > https://svn.apache.org/repos/asf/commons/proper/codec/tags/commons-codec-1.5-RC1 > > Site: > > http://people.apache.org/builds/commons/codec/1.5/RC1/site/index.html AIUI from the branding perspective: Ideally there should be a TM after the first use of Commons Codec, and it should be used as an adjective, e.g. Apache Commons Coded tm software is ... but these are not blockers, and can be fixed later. > Binaries: > > https://repository.apache.org/content/repositories/orgapachecommons-041/ Cannot find the signing key in the KEYS file:. http://www.apache.org/dist/commons/KEYS That must be fixed before release. Otherwise seems OK [I deleted the .asc.md5 and .asc.sha1 files] > > [ ] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because > > Thank you, > Gary > > http://garygregory.wordpress.com/ > http://garygregory.com/ > http://people.apache.org/~ggregory/ > http://twitter.com/GaryGregory > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[VOTE] Release Apache Commons Codec 1.5-RC1
[VOTE] Release Apache Commons Codec 1.5-RC1 Tag: https://svn.apache.org/repos/asf/commons/proper/codec/tags/commons-codec-1.5-RC1 Site: http://people.apache.org/builds/commons/codec/1.5/RC1/site/index.html Binaries: https://repository.apache.org/content/repositories/orgapachecommons-041/ [ ] +1 release it [ ] +0 go ahead I don't care [ ] -1 no, do not release it because Thank you, Gary http://garygregory.wordpress.com/ http://garygregory.com/ http://people.apache.org/~ggregory/ http://twitter.com/GaryGregory
Re: [continuum] BUILD FAILURE: Apache Commons - Commons Pool - Default Maven 2 Build Definition (Java 1.5)
On 24/03/2011 14:47, sebb wrote: > Done, I think Yep. Tx. Mark - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [continuum] BUILD FAILURE: Apache Commons - Commons Pool - Default Maven 2 Build Definition (Java 1.5)
Done, I think On 24 March 2011 14:41, Mark Thomas wrote: > On 24/03/2011 14:11, Continuum@vmbuild wrote: >> Online report : >> http://vmbuild.apache.org/continuum/buildResult.action?buildId=5563&projectId=98 > > This looks like a false positive. I did have a continuum account once > upon a time but it appears to have been deleted at some point. I have > recreated it (markt). If someone with admin karma to the commons group > could grant me the necessary karma, I'll kick off a new test run to see > if this was a one-off. > > Cheers, > > Mark > > - > 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: [continuum] BUILD FAILURE: Apache Commons - Commons Pool - Default Maven 2 Build Definition (Java 1.5)
On 24/03/2011 14:11, Continuum@vmbuild wrote: > Online report : > http://vmbuild.apache.org/continuum/buildResult.action?buildId=5563&projectId=98 This looks like a false positive. I did have a continuum account once upon a time but it appears to have been deleted at some point. I have recreated it (markt). If someone with admin karma to the commons group could grant me the necessary karma, I'll kick off a new test run to see if this was a one-off. Cheers, Mark - 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 Pool - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=5563&projectId=98 Build statistics: State: Failed Previous State: Ok Started at: Thu 24 Mar 2011 14:08:23 + Finished at: Thu 24 Mar 2011 14:11:33 + Total time: 3m 9s Build Trigger: Schedule Build Number: 65 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_22" Java(TM) SE Runtime Environment (build 1.6.0_22-b04) Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_22 Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-27-server" arch: "amd64" Family: "unix" SCM Changes: Changed: markt @ Thu 24 Mar 2011 11:25:33 + Comment: Add missing @Test annotations. Files changed: /commons/proper/pool/trunk/src/test/org/apache/commons/pool2/impl/TestGenericKeyedObjectPool.java ( 1084901 ) Changed: markt @ Thu 24 Mar 2011 11:32:07 + Comment: Additional fixes for POOL-180. Ensure the evictor tracks internal processing counts per key and remove unused keys only when they are truly unused. Files changed: /commons/proper/pool/trunk/src/java/org/apache/commons/pool2/impl/GenericKeyedObjectPool.java ( 1084904 ) /commons/proper/pool/trunk/src/test/org/apache/commons/pool2/impl/TestGenericKeyedObjectPool.java ( 1084904 ) Changed: simonetripodi @ Thu 24 Mar 2011 11:53:26 + Comment: re-introduced the groupId - even if inherited from the parent - to avoid people deploy components with wrong metadata Files changed: /commons/proper/pool/trunk/pom.xml ( 1084917 ) Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean install Arguments: --batch-mode -Pjava-1.5 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 (Java 1.5) Test Summary: Tests: 178 Failures: 1 Errors: 0 Success Rate: 99 Total time: 163.328 Test Failures: TestGenericObjectPool testEvictionWithNegativeNumTests : java.lang.AssertionError java.lang.AssertionError: Should at most 3 idle, found 6 at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.assertTrue(Assert.java:43) at org.apache.commons.pool2.impl.TestGenericObjectPool.testEvictionWithNegativeNumTests(TestGenericObjectPool.java:905) 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:592) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit
Re: svn commit: r1084776 - /commons/proper/pool/trunk/pom.xml
so I understad why you're worried about it :) I'm going to rollback last pom commit Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Thu, Mar 24, 2011 at 12:01 PM, sebb wrote: > On 24 March 2011 09:42, Simone Tripodi wrote: >> Hi Jorg, >> I agree with you, but I think we've enough flexibility that if the >> component needs to override the groupId, simply redeclare it. > > If the groupId is omitted, it's not clear whether the omission is > deliberate or was accidentally deleted. > >> BTW If we're changing the parent reference, maybe we need to to review >> the whole set of metadata, I won't expect that a component is released >> with overlooked groupId, do you? > > That has already happened - the groupId was changed in at least one > component as part of various updates, and the change was not noticed > during voting. > >> Simo >> >> http://people.apache.org/~simonetripodi/ >> http://www.99soft.org/ >> >> >> >> On Thu, Mar 24, 2011 at 9:01 AM, Jörg Schaible >> wrote: >>> sebb wrote: >>> On 24 March 2011 00:09, Niall Pemberton wrote: > On Thu, Mar 24, 2011 at 12:05 AM, sebb wrote: >> On 23 March 2011 23:37, Simone Tripodi wrote: >>> On Thu, Mar 24, 2011 at 12:28 AM, sebb wrote: On 23 March 2011 23:14, Simone Tripodi wrote: > I think maven best practice would suggest to avoid groupId > duplication - for pool2 we agreed to switch to o.a.c groupId. > which problems are you speaking about? I'm asking because I would > have missed something I don't know yet. I just mean that the POM should specify the groupId even if it is the same as the parent. >>> >>> I still don't understand the reason why it should do it, can you point >>> me to some doc? >> >> AFAIK, there is no such document. >> >> But it's important for people reading the POM to know immediately what >> the groupId is, without having to go searching for the parent. > > There is no need to go searching for the parent. You can just look at > the element's groupId in the POM you're reading. OK, but I still think it's risky to rely on inheritance for such an important value. In theory, the parent might be changed, e.g. to the Apache POM, as used in Common Site Also, having an explicit value documents that the groupId is being intentionally set for this component. >>> >>> The info is redundant, but I second Sebb here, simply because in Commons not >>> every component has necessarily the same groupId. Currently we switch from >>> the old M1-style groupId to this one only on purpose and therefore I prefer >>> also the explicit definition here. >>> >>> - Jörg >>> >>> >>> - >>> 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: [POOL] Ready for 1.5.6
On 23/03/2011 20:01, Mark Thomas wrote: > On 23/03/2011 19:54, Phil Steitz wrote: >> On 3/23/11 12:36 PM, Mark Thomas wrote: >>> Phil, >>> >>> I believe all the pool issues for 1.5.x have been resolved. Over to >>> you... :) >>> >> Thanks! You are awesome, Mark! >> >> I will finish reviewing your last set of commits and then roll an RC. >> >> Did you see my (hopefully baseless) memory leak fear about the fix >> for POOL-181? > > I just did. My mail was slow this afternoon. Looking at it now. I think > a few changes will be required. Changes complete and test cases updated. I think we are good to go now. Mark - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[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 158 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.002 sec Running org.apache.commons.proxy.provider.TestConstantProvider Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032 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.028 sec Running org.apache.commons.proxy.interceptor.TestInterceptorChain Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.commons.proxy.invoker.TestNullInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec Running org.apache.commons.proxy.exception.TestDelegateProviderException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.commons.proxy.invoker.TestChainInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.157 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.006 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: Thu Mar 24 11:22:56 UTC 2011 [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: http://vmgump.apache.
Re: svn commit: r1084776 - /commons/proper/pool/trunk/pom.xml
On 24 March 2011 09:42, Simone Tripodi wrote: > Hi Jorg, > I agree with you, but I think we've enough flexibility that if the > component needs to override the groupId, simply redeclare it. If the groupId is omitted, it's not clear whether the omission is deliberate or was accidentally deleted. > BTW If we're changing the parent reference, maybe we need to to review > the whole set of metadata, I won't expect that a component is released > with overlooked groupId, do you? That has already happened - the groupId was changed in at least one component as part of various updates, and the change was not noticed during voting. > Simo > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > > > On Thu, Mar 24, 2011 at 9:01 AM, Jörg Schaible > wrote: >> sebb wrote: >> >>> On 24 March 2011 00:09, Niall Pemberton wrote: On Thu, Mar 24, 2011 at 12:05 AM, sebb wrote: > On 23 March 2011 23:37, Simone Tripodi wrote: >> On Thu, Mar 24, 2011 at 12:28 AM, sebb wrote: >>> On 23 March 2011 23:14, Simone Tripodi >>> wrote: I think maven best practice would suggest to avoid groupId duplication - for pool2 we agreed to switch to o.a.c groupId. which problems are you speaking about? I'm asking because I would have missed something I don't know yet. >>> >>> I just mean that the POM should specify the groupId even if it is the >>> same as the parent. >>> >> >> I still don't understand the reason why it should do it, can you point >> me to some doc? > > AFAIK, there is no such document. > > But it's important for people reading the POM to know immediately what > the groupId is, without having to go searching for the parent. There is no need to go searching for the parent. You can just look at the element's groupId in the POM you're reading. >>> >>> OK, but I still think it's risky to rely on inheritance for such an >>> important value. >>> >>> In theory, the parent might be changed, e.g. to the Apache POM, as >>> used in Common Site >>> >>> Also, having an explicit value documents that the groupId is being >>> intentionally set for this component. >> >> The info is redundant, but I second Sebb here, simply because in Commons not >> every component has necessarily the same groupId. Currently we switch from >> the old M1-style groupId to this one only on purpose and therefore I prefer >> also the explicit definition here. >> >> - Jörg >> >> >> - >> 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
[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 158 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 --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 - --- T E S T S --- Running org.apache.commons.scxml.invoke.InvokeTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.562 sec Running org.apache.commons.scxml.test.TestingTestSuite Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running org.apache.commons.scxml.env.EnvTestSuite Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.213 sec Running org.apache.commons.scxml.SCXMLTestSuite Tests run: 71, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.962 sec <<< FAILURE! Running org.apache.commons.scxml.issues.IssuesTestSuite Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.341 sec Running org.apache.commons.scxml.model.ModelTestSuite Tests run: 78, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.279 sec <<< FAILURE! Running org.apache.commons.scxml.env.faces.EnvFacesTestSuite Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.scxml.semantics.SemanticsTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.scxml.env.jsp.EnvJspTestSuite Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.049 sec Running org.apache.commons.scxml.env.jexl.EnvJexlTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032 sec Running org.apache.commons.scxml.env.servlet.EnvServletTestSuite Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.scxml.io.IOTestSuite Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.374 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: Thu Mar 24 10:31:45 UTC 2011 [INFO] Final Memory: 25M/61M [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 Apache Gump(TM) version 2.3. Gump Run 05000624032011, vmgump.apache.org:vmgump:05000624032011 Gump E-mail Identifier (unique wi
[GUMP@vmgump]: Project commons-vfs2 (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 has an issue affecting its community integration.
This issue affects 7 projects,
and has been outstanding for 41 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 : Apache Commons
- commons-configuration-test : Apache Commons
- commons-vfs2 : Apache Commons
- commons-vfs2-sandbox : Apache Commons
- commons-vfs2-test : Apache Commons
- jakarta-turbine-jcs : Cache
- jcs : Cache
Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-vfs2/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-vfs2-*[0-9T].jar] identifier set to project
name
-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- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-vfs2/gump_work/build_apache-commons_commons-vfs2.html
Work Name: build_apache-commons_commons-vfs2 (Type: Build)
Work ended in a state of : Failed
Elapsed: 37 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --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
-
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[move] Moving 2 files to
/srv/gump/public/workspace/apache-commons/vfs/core/target/test-classes/test-data/code
[INFO] Executed tasks
[WARNING] DEPRECATED [systemProperties]: Use systemPropertyVariables instead.
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/srv/gump/public/workspace/apache-commons/vfs/core/target/commons-vfs2-2.0-SNAPSHOT.jar
[INFO] [jar:test-jar {execution: default}]
[INFO] Building jar:
/srv/gump/public/workspace/apache-commons/vfs/core/target/commons-vfs2-2.0-SNAPSHOT-tests.jar
[INFO]
[INFO] Building Commons VFS Examples
[INFO]task-segment: [package]
[INFO]
[INFO] [antrun:run {execution: javadoc.resources}]
[INFO] Executing tasks
[INFO] Executed tasks
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource to META-INF
[INFO] Copying 1 resource to META-INF
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 5 source files to
/srv/gump/public/workspace/apache-commons/vfs/examples/target/classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/srv/gump/public/workspace/apache-commons/vfs/examples/src/main/java/org/apache/commons/vfs2/libcheck/FtpCheck.java:[75,46]
cannot find symbol
symbol : method getSystemName()
location: class org.apache.commons.net.ftp.FTPClient
[INFO] 1error
[INFO] -
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/srv/gump/public/workspace/apache-commons/vfs/examples/src/main/java/org/apache/commons/vfs2/libcheck/FtpCheck.java:[75,46]
cannot find symbol
symbol : method getSystemName()
location: class org.apache.commons.net.ftp.FTPClient
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 36 seconds
[INFO] Finished at: Thu Mar 24 10:20:14 UTC 2011
[INFO] Final Memory: 46M/110M
[INFO]
-
To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-vfs2/rss.xml
- Atom:
http://vmgump.apache.org/gump/public/apache-commons/commons-vfs2/atom.xml
=
Re: svn commit: r1084642 - /commons/proper/pool/trunk/src/java/org/apache/commons/pool2/impl/GenericKeyedObjectPool.java
On 23/03/2011 22:13, Phil Steitz wrote: > On 3/23/11 2:01 PM, Mark Thomas wrote: >> On 23/03/2011 17:46, Phil Steitz wrote: >>> Do we need to worry about leaking memory here due to things never >>> getting removed from _poolMap, _poolList? >> I don't think so. The entries should only exit in _poolMap and _poolList >> while associated objects exist. >> > Looking carefully at both 1.5.5 and 1.5.x current code, I can see > the situation is better now; but I still can't see _poolMap reliably > cleaned up if clear is invoked when an instance failing validation > is in process of being destroyed. I am not sure there is an easy > way to fix this, since we need to keep the _poolMap entry around to > keep accounting correct. Thanks for the analysis. In that scenario, allowing for the synchronisation, there are four different code blocks that could end being the lest to execute: - clear() -> destroy(Map, KeyedPoolableObjectFactory) -> clean up - evict() -> clean up needs to move to end of method - borrowObject() -> no clean up (doesn't matter since we need to create) - return() -> no clean up (can be added) I have a patch that makes the necessary changes (and fixes a unit test that fails now the keys are retained to track active count). I just need to run the unit tests and port the changes to trunk. Mark > > Phil > >>> Also, IIUC what is going on here, we need to make a similar change >>> the evict() where the last instance in a keyed pool is evicted. >> It certainly looks like it. However, this is highlighting some issues (I >> think in the tests). I'll try and look at this tomorrow. >> >> Mark >> >> - >> 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: svn commit: r1084776 - /commons/proper/pool/trunk/pom.xml
Hi Jorg, I agree with you, but I think we've enough flexibility that if the component needs to override the groupId, simply redeclare it. BTW If we're changing the parent reference, maybe we need to to review the whole set of metadata, I won't expect that a component is released with overlooked groupId, do you? Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Thu, Mar 24, 2011 at 9:01 AM, Jörg Schaible wrote: > sebb wrote: > >> On 24 March 2011 00:09, Niall Pemberton wrote: >>> On Thu, Mar 24, 2011 at 12:05 AM, sebb wrote: On 23 March 2011 23:37, Simone Tripodi wrote: > On Thu, Mar 24, 2011 at 12:28 AM, sebb wrote: >> On 23 March 2011 23:14, Simone Tripodi >> wrote: >>> I think maven best practice would suggest to avoid groupId >>> duplication - for pool2 we agreed to switch to o.a.c groupId. >>> which problems are you speaking about? I'm asking because I would >>> have missed something I don't know yet. >> >> I just mean that the POM should specify the groupId even if it is the >> same as the parent. >> > > I still don't understand the reason why it should do it, can you point > me to some doc? AFAIK, there is no such document. But it's important for people reading the POM to know immediately what the groupId is, without having to go searching for the parent. >>> >>> There is no need to go searching for the parent. You can just look at >>> the element's groupId in the POM you're reading. >> >> OK, but I still think it's risky to rely on inheritance for such an >> important value. >> >> In theory, the parent might be changed, e.g. to the Apache POM, as >> used in Common Site >> >> Also, having an explicit value documents that the groupId is being >> intentionally set for this component. > > The info is redundant, but I second Sebb here, simply because in Commons not > every component has necessarily the same groupId. Currently we switch from > the old M1-style groupId to this one only on purpose and therefore I prefer > also the explicit definition here. > > - Jörg > > > - > 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
[Commons Wiki] Update of "CommonsOsgi" by NiallPemberton
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CommonsOsgi" page has been changed by NiallPemberton. http://wiki.apache.org/commons/CommonsOsgi?action=diff&rev1=36&rev2=37 -- set up. Therefore adding OSGi attributes to commons-logging is not useful, as commons-logging is not usable in an OSGi environment. See [[http://commons.markmail.org/message/kdnjlbokvuiigcew|this thread]] and - [[http://wiki.ops4j.org/dokuwiki/doku.php?id=pax:logging|Pax-logging]] + [[http://wiki.ops4j.org/display/paxlogging/Pax+Logging]] Having said that the Felix project has a bundle to re-package logging - see [[http://svn.apache.org/repos/asf/felix/trunk/commons/commons-logging/pom.xml|here]] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[vfs] Does it support FTPS with user certificates
I believe we have the FTPS support in the trunk of the vfs. Does it support the user certificates as well? Thanks, -- Supun Kamburugamuva Technical Lead & Product Manager, WSO2 Inc.; http://wso2.com Member, Apache Software Foundation; http://www.apache.org WSO2 Inc.; http://wso2.org E-mail: su...@wso2.com; Mobile: +94 77 431 3585 Blog: http://supunk.blogspot.com
Re: svn commit: r1084776 - /commons/proper/pool/trunk/pom.xml
sebb wrote: > On 24 March 2011 00:09, Niall Pemberton wrote: >> On Thu, Mar 24, 2011 at 12:05 AM, sebb wrote: >>> On 23 March 2011 23:37, Simone Tripodi wrote: On Thu, Mar 24, 2011 at 12:28 AM, sebb wrote: > On 23 March 2011 23:14, Simone Tripodi > wrote: >> I think maven best practice would suggest to avoid groupId >> duplication - for pool2 we agreed to switch to o.a.c groupId. >> which problems are you speaking about? I'm asking because I would >> have missed something I don't know yet. > > I just mean that the POM should specify the groupId even if it is the > same as the parent. > I still don't understand the reason why it should do it, can you point me to some doc? >>> >>> AFAIK, there is no such document. >>> >>> But it's important for people reading the POM to know immediately what >>> the groupId is, without having to go searching for the parent. >> >> There is no need to go searching for the parent. You can just look at >> the element's groupId in the POM you're reading. > > OK, but I still think it's risky to rely on inheritance for such an > important value. > > In theory, the parent might be changed, e.g. to the Apache POM, as > used in Common Site > > Also, having an explicit value documents that the groupId is being > intentionally set for this component. The info is redundant, but I second Sebb here, simply because in Commons not every component has necessarily the same groupId. Currently we switch from the old M1-style groupId to this one only on purpose and therefore I prefer also the explicit definition here. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [discuss][Digester] The future of Digester an the Digester3 in sandbox - Take2
hahaha thanks! BTW I really hope there will be another chance to come back in charge with this proposal :) Have a nice day, Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Thu, Mar 24, 2011 at 2:30 AM, Matt Benson wrote: > On Wed, Mar 23, 2011 at 6:50 PM, Simone Tripodi > wrote: >> Hi Matt!!! >> I noticed 2 important points I'd like to discuss: >> >> 1) generally speaking, the bigger part of the users are lazy: they >> just want to grab latest released artifact of XXX component with Maven >> and use it, so it is hard to obtain feedbacks from APIs not released >> yet; >> 2) committers/PMCs interested on Digester is reduced: we got two +1s, >> one +0 and I didn't express my opinion (If I would have done it, in my >> country they would have called me Mafia guy :D ) >> >> I didn't understand when you wrote "I'm certainly not going to twist >> your arm": of course you wouldn't do it physically :D but I didn't >> understand in which sense :P >> > > :) Just an expression meaning to try to make you do something against > your will. > > Matt > >> Have a nice day, all the best! >> Simo >> >> http://people.apache.org/~simonetripodi/ >> http://www.99soft.org/ >> >> >> >> On Wed, Mar 23, 2011 at 1:03 PM, Matt Benson wrote: >>> On Wed, Mar 23, 2011 at 6:37 AM, Simone Tripodi >>> wrote: Hi all guys, looks like there's not enough activity/interest on new Digester, I suggest to suspend this topic for a while and come speaking about it until there will be interest from the users. Thanks to all that took part of the discussion! All the best, have a nice day, Simo >>> >>> Personally, I think that just because the users aren't clamoring for >>> the new API doesn't mean they wouldn't like it if Digester3 were >>> released. At the same time, I'm certainly not going to twist your >>> arm. >>> >>> Matt >>> http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Sat, Mar 19, 2011 at 9:51 PM, Simone Tripodi wrote: > Hi all, > thanks for the trust guys!!! I won't express my vote, it would be too > incorrect IMHO. I'll keep my finger crossed to see at least the 3 > consensus :) > Have a nice weekend! > Simo > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > > > On Sat, Mar 19, 2011 at 8:27 PM, Matt Benson wrote: >> >> On Mar 19, 2011, at 11:05 AM, Rahul Akolkar wrote: >> >>> On Sat, Mar 19, 2011 at 11:05 AM, Phil Steitz >>> wrote: On 3/19/11 4:54 AM, Simone Tripodi wrote: > Hi Rahul, > thanks once again for the wise suggestions, much more than > appreciated! > > I underestimated the importance of the users over the active > developers, so I totally agree with you, moving to dormant is > premature. > > I was aware about breaking APIs compatibility, since we had to face > the same problem also in [pool2], I thought it would have been a good > idea implementing the sandbox in the o.a.c.digester3[1] package, looks > like it is compliant to the suggestions you proposed. > > I like your idea of branching 1.X, 2.X and put 3 on trunk, shall we > call a vote before going on? +1 I don't think we need a VOTE on this, I would say wait a couple of more days to make sure we have (lazy) consensus and then just do it. >>> >>> >>> Not that I care for more process, but I'd like to see 3+ of us say >>> this is the API they'd like to see for digester3. We also generally >>> require votes for getting stuff out of sandbox so a vote may not be a >>> bad idea (even if this isn't a new component, its a new API -- and >>> somewhere in there, the lines are blurred). I'm +0. >>> >> >> I hesitate to throw in an opinion as I've never really used digester, >> but I quite like the API personally, and would +1 this. >> >> Matt >> >>> -Rahul >>> >>> - >>> 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: [LOGGING] latest 1.1.1 release is not a valid OSGi bundle
Thanks Niall, I totally missed that page, you saved my life! :) Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Thu, Mar 24, 2011 at 1:01 AM, Niall Pemberton wrote: > On Wed, Mar 23, 2011 at 11:55 PM, Simone Tripodi > wrote: >> Hi all guys, >> I just got an error in my OSGi environment because >> commons-logging-1.1.1 doesn't have the required OSGi metadata in the >> MANIFEST. >> Would you agree on releasing a 1.1.2 just to add this metadata? > > Theres a note on Commons Logging on the following page: > > http://wiki.apache.org/commons/CommonsOsgi > > Niall > >> Many thanks in advance! >> 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
