Re: Nexus vs rsync-repository releases
Le 03/08/2011 08:40, Phil Steitz a écrit : On 8/2/11 11:30 PM, Jochen Wiedmann wrote: On Wed, Aug 3, 2011 at 8:28 AM, Phil Steitz wrote: Nothing, other than that is exactly what I do and I know exactly what is going on. I don't see any real saving, that's all and I see no need to bring in proprietary gui-based software into the mix or to wget stuff from remote hosts. Nobody else seems to care about this, but you actually should perform a step that I don't - which is to verify the hashes after you move the stuff to dist/ Why should I? They have been built by Maven or Nexus automatically? When you transfer files on the Internet, they can get corrupted in transit. This is why we *have* hashes on the files. When you put the files on p.a.o and we VOTE on the bits there, you can just move them to /dist without worrying about integrity. And I seriously hope nothing is being "built by nexus" :) I am also worried about a closed tool like Nexus being used to publish Apache stuff. Luc Phil - 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: Nexus vs rsync-repository releases
On 8/2/11 11:30 PM, Jochen Wiedmann wrote: > On Wed, Aug 3, 2011 at 8:28 AM, Phil Steitz wrote: > >> Nothing, other than that is exactly what I do and I know exactly >> what is going on. I don't see any real saving, that's all and I see >> no need to bring in proprietary gui-based software into the mix or >> to wget stuff from remote hosts. Nobody else seems to care about >> this, but you actually should perform a step that I don't - which is >> to verify the hashes after you move the stuff to dist/ > Why should I? They have been built by Maven or Nexus automatically? When you transfer files on the Internet, they can get corrupted in transit. This is why we *have* hashes on the files. When you put the files on p.a.o and we VOTE on the bits there, you can just move them to /dist without worrying about integrity. And I seriously hope nothing is being "built by nexus" :) Phil > > - 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 CLI - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10810&projectId=67 Build statistics: State: Failed Previous State: Failed Started at: Wed 3 Aug 2011 06:38:40 + Finished at: Wed 3 Aug 2011 06:38:52 + Total time: 12s Build Trigger: Forced Build Number: 23 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean install deploy 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: 361 Failures: 0 Errors: 0 Success Rate: 100 Total time: 0.3438 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Nexus vs rsync-repository releases
On Wed, Aug 3, 2011 at 8:28 AM, Phil Steitz wrote: > Nothing, other than that is exactly what I do and I know exactly > what is going on. I don't see any real saving, that's all and I see > no need to bring in proprietary gui-based software into the mix or > to wget stuff from remote hosts. Nobody else seems to care about > this, but you actually should perform a step that I don't - which is > to verify the hashes after you move the stuff to dist/ Why should I? They have been built by Maven or Nexus automatically? -- Capitalism is the astounding belief that the most wickedest of men will do the most wickedest of things for the greatest good of everyone. John Maynard Keynes (http://en.wikiquote.org/wiki/Keynes) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Nexus vs rsync-repository releases
On 8/2/11 11:09 PM, Jochen Wiedmann wrote: > On Wed, Aug 3, 2011 at 7:51 AM, Phil Steitz wrote: > >> I am not so sure about that. I guess it depends on what kind of >> simple scripts you are willing to use to automate things and how >> much you care about being certain that that things are working and >> you know exactly what is going on. Personally, I would prefer that >> this machinery be visible and not require web gui games or plaintext >> passwords to work. I like the way tomcat does this and I will >> volunteer to develop and document a similar set of Ant tasks for >> Commons if others are willing to move back to replicating o.a.c >> groupIds from p.a.o. > Phil, my "simple script" is the POM. With Nexus, my manual steps are > typically reduced to copying the -src and -bin files out of the > repository (wget's good for that and it copies the whole directory at > one go) and copying these to the dist directory. Honestly, there are > some things remaining like setting the -current links, updating the > README and perhaps the KEYS file and fixing the permissions. But these > are left to do anyways. > > What's wrong with that procedure? Nothing, other than that is exactly what I do and I know exactly what is going on. I don't see any real saving, that's all and I see no need to bring in proprietary gui-based software into the mix or to wget stuff from remote hosts. Nobody else seems to care about this, but you actually should perform a step that I don't - which is to verify the hashes after you move the stuff to dist/ Phil > > Jochen > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Nexus vs rsync-repository releases
On Wed, Aug 3, 2011 at 7:51 AM, Phil Steitz wrote: > I am not so sure about that. I guess it depends on what kind of > simple scripts you are willing to use to automate things and how > much you care about being certain that that things are working and > you know exactly what is going on. Personally, I would prefer that > this machinery be visible and not require web gui games or plaintext > passwords to work. I like the way tomcat does this and I will > volunteer to develop and document a similar set of Ant tasks for > Commons if others are willing to move back to replicating o.a.c > groupIds from p.a.o. Phil, my "simple script" is the POM. With Nexus, my manual steps are typically reduced to copying the -src and -bin files out of the repository (wget's good for that and it copies the whole directory at one go) and copying these to the dist directory. Honestly, there are some things remaining like setting the -current links, updating the README and perhaps the KEYS file and fixing the permissions. But these are left to do anyways. What's wrong with that procedure? Jochen -- Capitalism is the astounding belief that the most wickedest of men will do the most wickedest of things for the greatest good of everyone. John Maynard Keynes (http://en.wikiquote.org/wiki/Keynes) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [math] Utility classes for testing purposes
On 8/2/11 10:48 PM, Sebastien Brisard wrote: > Hi, > I'm finalizing unit tests for the conjugate gradient method, for which I'm > using Hilbert matrices (see http://en.wikipedia.org/wiki/Hilbert_matrix). > These matrices are nice because > i. they are symmetric, positive definite, > ii. they are ill-conditioned, > iii. their inverse is known in closed-form. > > I therefore implemented HilbertMatrix and InverseHilbertMatrix as > RealLinearOperator. These two classes are intended for testing purposes only, > but I do not want to embed them in ConjugateGradientTest, as they might be > used to test other iterative solvers as well. My question is simple: where > (meaning: which package) should these two classes go? Would o.a.c.math.linear > (in the src/test/java directory) be suitable? That would be fine, yes. Phil > Any better suggestion? > > Thanks beforehand, > Sebastien > > - > 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: Nexus vs rsync-repository releases
On 8/2/11 10:36 PM, Jochen Wiedmann wrote: > On Tue, Aug 2, 2011 at 4:29 PM, Mark Thomas wrote: > >> What benefits do we get by using Nexus > A real lot of work saved. (Beleave me. I've been RM for the same > projects with and without Nexus and it's really a difference.) > I am not so sure about that. I guess it depends on what kind of simple scripts you are willing to use to automate things and how much you care about being certain that that things are working and you know exactly what is going on. Personally, I would prefer that this machinery be visible and not require web gui games or plaintext passwords to work. I like the way tomcat does this and I will volunteer to develop and document a similar set of Ant tasks for Commons if others are willing to move back to replicating o.a.c groupIds from p.a.o. Phil > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [logging] logging vs slf4j
On Tue, Aug 2, 2011 at 1:59 AM, Emmanuel Bourg wrote: > Le 28/07/2011 22:01, Henri Yandell a écrit : >> >> Personally I'm happy for commons-logging to die. :) > > Yeah let's use java.util.logging instead :) Primarily that I don't get the feeling we have a major community of developers on c-logging. We implemented it because we needed something for our other components (though many simply chose not to log), but it was never the passion of anybody here (hopefully not an incorrect statement). Robert, Simon and others put in tons of good work, but I feel that was duty not passion. So happy to see it die because it's something that's headed to dormancy (be it stable or not). Hen - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[math] Utility classes for testing purposes
Hi, I'm finalizing unit tests for the conjugate gradient method, for which I'm using Hilbert matrices (see http://en.wikipedia.org/wiki/Hilbert_matrix). These matrices are nice because i. they are symmetric, positive definite, ii. they are ill-conditioned, iii. their inverse is known in closed-form. I therefore implemented HilbertMatrix and InverseHilbertMatrix as RealLinearOperator. These two classes are intended for testing purposes only, but I do not want to embed them in ConjugateGradientTest, as they might be used to test other iterative solvers as well. My question is simple: where (meaning: which package) should these two classes go? Would o.a.c.math.linear (in the src/test/java directory) be suitable? Any better suggestion? Thanks beforehand, Sebastien - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [LANG] Proposing 3.0.1
I've updated the site. * Checkstyle: A javadoc item that Matt has said he'll work on. * FindBugs: Complains about an NPE, however it's not true and is because FindBugs doesn't understand our Validate library. * PMD: Down to one item to do with equals + hashcode. Might be worth fixing, but no rush. Cobertura looks a bit weak for a couple of classes; TypeUtils and ToStringStyle stand out. Again no blocker. I've double checked that the items mentioned in Clirr have @since 3.0.1 (apart from any very recent changes, but IIRC they looked good too). One oddity in Clirr is that building under JDK 1.6 identifies enums as no longer having final values() methods. Interesting item :) Should go away when I build a release candidate under JDK 1.5 (Mac=1.6; RC's happen on my Linux machine). Generally things look good. Two JIRA items outstanding, neither are blockers and I'll be looking to push both to 3.0.2. Hen On Tue, Aug 2, 2011 at 12:49 AM, Henri Yandell wrote: > Here's a generated site: > > http://people.apache.org/~bayard/commons-lang-3.0.1-SNAPSHOT-site/ > > Review the additions in the clirr report. Note the checkstyle and > findbugs reports have items that need cleanup prior to release. > > Hen > > On Tue, Aug 2, 2011 at 12:27 AM, Henri Yandell wrote: >> I'd like to release 3.0.1 of Lang. It would contain the following 11 fixes: >> >> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+LANG+AND+fixVersion+%3D+%223.0.1%22+AND+resolution+in+%28Fixed%2C+%22Won%27t+Fix%22%2C+Duplicate%2C+Invalid%2C+Incomplete%2C+%22Cannot+Reproduce%22%2C+Later%2C+%22Not+A+Problem%22%2C+Unresolved%29 >> >> LANG-611 Consider improvements in LANG-396 >> LANG-626 object cloning with SerializationUtils has classloader >> problems with no workaround >> LANG-708 StringEscapeUtils.escapeEcmaScript from lang3 cuts off long >> unicode string >> LANG-717 Specify source encoding for build >> LANG-720 StringEscapeUtils.escapeXml(input) outputs wrong results >> when an input contains characters in Supplementary Planes. >> LANG-721 Complement ArrayUtils.addAll() variants with by-index and >> by-value removal methods >> LANG-722 Add BooleanUtils.and/or varargs methods to complement xor >> LANG-723 Add mode and median Comparable... methods to ObjectUtils >> LANG-726 Add a method e.g. Range >> Range.intersectionWith(Range) >> LANG-727 ToStringBuilderTest.testReflectionHierarchyArrayList fails >> with IBM JDK 6 >> LANG-730 EnumSet -> BitVector >> >> Two issues were pushed back to 3.0.2 as 'not ready', and there are 54 >> items in 3.x for consideration. >> >> The biggest issue needing feedback would (imo) be LANG-626. >> >> I'll get a clirr report put together (and update the site); for now >> use this thread if you have any objections to a 3.0.1 release. >> >> Hen >> > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Nexus vs rsync-repository releases
On Tue, Aug 2, 2011 at 4:29 PM, Mark Thomas wrote: > What benefits do we get by using Nexus A real lot of work saved. (Beleave me. I've been RM for the same projects with and without Nexus and it's really a difference.) -- Capitalism is the astounding belief that the most wickedest of men will do the most wickedest of things for the greatest good of everyone. John Maynard Keynes (http://en.wikiquote.org/wiki/Keynes) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Nexus vs rsync-repository releases
On Tue, Aug 2, 2011 at 9:30 PM, Phil Steitz wrote: > On 8/2/11 5:22 PM, Henri Yandell wrote: >> On Tue, Aug 2, 2011 at 7:23 AM, Emmanuel Bourg wrote: >>> Are we still going to deploy Maven artifacts by SCPing to >>> m2-ibiblio-rsync-repository on people.apache.org? >>> >>> I've been discussing the permissions issue for the old groupIds on Nexus >>> with the Infra team (i.e components using the old groupId >>> commons- need a specific configuration on the snapshot and >>> release repositories). >>> >>> Brian Demers kindly proposed to allow the deployment of all commons-* groups >>> on Nexus, but it would require to block the deployment through >>> people.apache.org to avoid metadata conflicts. >>> >>> Do we all agree on using exclusively Nexus for our releases? > > I would prefer to leave the door open to release more point releases > of [pool] and [dbcp] 1.x using the working scripts that i have, so > pls do not nuke those. The new versions are in the org.apache > groupId tree, so we will have no choice but to use nexus for those. > > I will have agree to use nexus for the maven repo bits, but prefer > to create the actual release artifacts locally, examine them, call a > VOTE on them and move the same bits to /dist. Personally, I would > rather see us move back the other way (use the Tomcat setup, with > Ant tasks pushing to p.a.o/rysnch), but I can see I am in the > minority here, so will not stand in the way. Well, I'm in the same minority and I'm not aware it's a minority (have we taken a vote from those release managing?). Nexus, Maven release-plugin, they all fire off my keep-it-simple warning flags. They mistake magic for simplicity. Hen - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[RESULT][VOTE][DAEMON] Release Apache Commons Daemon 1.0.7
With my implicit +1 we have 6 binding votes As such, Daemon 1.0.7 has been voted as stable. I'll copy the files to the dist, and make ANN later this week. Thanks to all who helped testing! Regards -- ^TM - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Nexus vs rsync-repository releases
On 8/2/11 5:22 PM, Henri Yandell wrote: > On Tue, Aug 2, 2011 at 7:23 AM, Emmanuel Bourg wrote: >> Are we still going to deploy Maven artifacts by SCPing to >> m2-ibiblio-rsync-repository on people.apache.org? >> >> I've been discussing the permissions issue for the old groupIds on Nexus >> with the Infra team (i.e components using the old groupId >> commons- need a specific configuration on the snapshot and >> release repositories). >> >> Brian Demers kindly proposed to allow the deployment of all commons-* groups >> on Nexus, but it would require to block the deployment through >> people.apache.org to avoid metadata conflicts. >> >> Do we all agree on using exclusively Nexus for our releases? I would prefer to leave the door open to release more point releases of [pool] and [dbcp] 1.x using the working scripts that i have, so pls do not nuke those. The new versions are in the org.apache groupId tree, so we will have no choice but to use nexus for those. I will have agree to use nexus for the maven repo bits, but prefer to create the actual release artifacts locally, examine them, call a VOTE on them and move the same bits to /dist. Personally, I would rather see us move back the other way (use the Tomcat setup, with Ant tasks pushing to p.a.o/rysnch), but I can see I am in the minority here, so will not stand in the way. Phil > I use the Commons release process: > > http://commons.apache.org/releases/index.html > > Meaning, that if you replace that with something of equal depth that > is Nexus related, then I'll do my best to adapt. Until then I'll > follow the docs (and then upload my Maven jars as an afterthought). > > Please make sure there's no part of the doc that says "put your > passphrase/password in a plaintext file" :) > > Hen > > - > 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: Nexus vs rsync-repository releases
On Tue, Aug 2, 2011 at 7:23 AM, Emmanuel Bourg wrote: > Are we still going to deploy Maven artifacts by SCPing to > m2-ibiblio-rsync-repository on people.apache.org? > > I've been discussing the permissions issue for the old groupIds on Nexus > with the Infra team (i.e components using the old groupId > commons- need a specific configuration on the snapshot and > release repositories). > > Brian Demers kindly proposed to allow the deployment of all commons-* groups > on Nexus, but it would require to block the deployment through > people.apache.org to avoid metadata conflicts. > > Do we all agree on using exclusively Nexus for our releases? I use the Commons release process: http://commons.apache.org/releases/index.html Meaning, that if you replace that with something of equal depth that is Nexus related, then I'll do my best to adapt. Until then I'll follow the docs (and then upload my Maven jars as an afterthought). Please make sure there's no part of the doc that says "put your passphrase/password in a plaintext file" :) Hen - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [LANG] Proposing 3.0.1
Jörg Schaible wrote: [snip] > I'd like to add first a getRawMessage() calling super.getMessage() to > Contexted(Runtime)Exception as counter part to the > getFormattedExceptionMessage(). I'll do it this evening. Done. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [LANG] Proposing 3.0.1
I love that we are still rolling along here :) Gary On Aug 2, 2011, at 3:50, Henri Yandell wrote: > Here's a generated site: > >http://people.apache.org/~bayard/commons-lang-3.0.1-SNAPSHOT-site/ > > Review the additions in the clirr report. Note the checkstyle and > findbugs reports have items that need cleanup prior to release. > > Hen > > On Tue, Aug 2, 2011 at 12:27 AM, Henri Yandell wrote: >> I'd like to release 3.0.1 of Lang. It would contain the following 11 fixes: >> >> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+LANG+AND+fixVersion+%3D+%223.0.1%22+AND+resolution+in+%28Fixed%2C+%22Won%27t+Fix%22%2C+Duplicate%2C+Invalid%2C+Incomplete%2C+%22Cannot+Reproduce%22%2C+Later%2C+%22Not+A+Problem%22%2C+Unresolved%29 >> >> LANG-611Consider improvements in LANG-396 >> LANG-626object cloning with SerializationUtils has classloader >> problems with no workaround >> LANG-708StringEscapeUtils.escapeEcmaScript from lang3 cuts off long >> unicode string >> LANG-717Specify source encoding for build >> LANG-720StringEscapeUtils.escapeXml(input) outputs wrong results >> when an input contains characters in Supplementary Planes. >> LANG-721Complement ArrayUtils.addAll() variants with by-index and >> by-value removal methods >> LANG-722Add BooleanUtils.and/or varargs methods to complement xor >> LANG-723Add mode and median Comparable... methods to ObjectUtils >> LANG-726Add a method e.g. Range >> Range.intersectionWith(Range) >> LANG-727ToStringBuilderTest.testReflectionHierarchyArrayList fails >> with IBM JDK 6 >> LANG-730EnumSet -> BitVector >> >> Two issues were pushed back to 3.0.2 as 'not ready', and there are 54 >> items in 3.x for consideration. >> >> The biggest issue needing feedback would (imo) be LANG-626. >> >> I'll get a clirr report put together (and update the site); for now >> use this thread if you have any objections to a 3.0.1 release. >> >> Hen >> > > - > 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 Math - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10785&projectId=206 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 16:17:00 + Finished at: Tue 2 Aug 2011 16:18:27 + Total time: 1m 27s Build Trigger: Forced Build Number: 75 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 2451 Failures: 0 Errors: 0 Success Rate: 100 Total time: 53.13398 - 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 Lang - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10784&projectId=136 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 16:16:25 + Finished at: Tue 2 Aug 2011 16:16:58 + Total time: 32s Build Trigger: Forced Build Number: 31 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 1973 Failures: 0 Errors: 0 Success Rate: 100 Total time: 13.338998 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Is this really needed !? Was: [continuum] BUILD FAILURE: XXX
Le 02/08/2011 18:04, Mladen Turk a écrit : I see there is online report. Is there really a need for such high volume of messages to the developers list like there's not enough email messages already? Yesterday there was 30 messages like those, so I suppose the same number is going to hit us today. Couldn't the parties interested in those mails either just check the web page or create a separate mailing list? Sorry for the spam, this is the result of trials and errors in the process of configuring Continuum to deploy the snapshots. I'm to blame for the first wave, I expected to build only one project but everything went off. The second wave was triggered after Brett Porter configured the build account allowed to deploy the artifacts on the server hosting Continuum. Emmanuel Bourg - 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 Javaflow (Sandbox) - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10775&projectId=116 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 16:12:15 + Finished at: Tue 2 Aug 2011 16:12:27 + Total time: 12s Build Trigger: Forced Build Number: 8 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 18 Failures: 0 Errors: 0 Success Rate: 100 Total time: 0.337 - 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 JCI - Continue test if possible; use Java 1.5
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10773&projectId=108 Build statistics: State: Failed Previous State: Failed Started at: Tue 2 Aug 2011 16:10:21 + Finished at: Tue 2 Aug 2011 16:12:02 + Total time: 1m 41s Build Trigger: Forced Build Number: 4 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean install Arguments: --batch-mode -fae -Pjava-1.5 Build Fresh: false Always Build: false Default Build Definition: true Schedule: COMMONS_SCHEDULE Profile Name: Maven 2.2.1 Description: Continue test if possible; use Java 1.5 Test Summary: Tests: 81 Failures: 1 Errors: 0 Success Rate: 98 Total time: 173.875 Test Failures: EclipseJavaCompilerTestCase testAdditionalTopLevelClassCompile : junit.framework.AssertionFailedError junit.framework.AssertionFailedError: The type AdditionalTopLevel collides with a package, expected:<0> but was:<1> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:280) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:198) at org.apache.commons.jci.compilers.AbstractCompilerTestCase.testAdditionalTopLevelClassCompile(AbstractCompilerTestCase.java:336) 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 junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) 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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102) at org.apache.maven.surefire.Surefire.run(Surefire.java:180) 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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional comma
[continuum] BUILD FAILURE: Apache Commons - Commons Net - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10772&projectId=107 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 16:08:57 + Finished at: Tue 2 Aug 2011 16:10:19 + Total time: 1m 21s Build Trigger: Forced Build Number: 160 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 153 Failures: 0 Errors: 0 Success Rate: 100 Total time: 60.458996 - 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 Validator - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10771&projectId=106 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 16:08:26 + Finished at: Tue 2 Aug 2011 16:08:56 + Total time: 29s Build Trigger: Forced Build Number: 18 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 414 Failures: 0 Errors: 0 Success Rate: 100 Total time: 5.378999 - 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 SCXML - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10770&projectId=101 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 16:08:02 + Finished at: Tue 2 Aug 2011 16:08:25 + Total time: 22s Build Trigger: Forced Build Number: 13 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 229 Failures: 0 Errors: 0 Success Rate: 100 Total time: 7.342999 - 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 Primitives - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10768&projectId=99 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 16:07:22 + Finished at: Tue 2 Aug 2011 16:07:44 + Total time: 21s Build Trigger: Forced Build Number: 4 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 4452 Failures: 0 Errors: 0 Success Rate: 100 Total time: 3.551 - 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 Logging - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10766&projectId=96 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 16:05:27 + Finished at: Tue 2 Aug 2011 16:05:41 + Total time: 14s Build Trigger: Forced Build Number: 6 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 88 Failures: 0 Errors: 0 Success Rate: 100 Total time: 1.263 - 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 JXPath - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10764&projectId=94 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 16:04:21 + Finished at: Tue 2 Aug 2011 16:04:42 + Total time: 21s Build Trigger: Forced Build Number: 7 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 384 Failures: 0 Errors: 0 Success Rate: 100 Total time: 6.516 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Is this really needed !? Was: [continuum] BUILD FAILURE: XXX
On 08/02/2011 06:00 PM, Continuum@vmbuild wrote: Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10757&projectId=78 I see there is online report. Is there really a need for such high volume of messages to the developers list like there's not enough email messages already? Yesterday there was 30 messages like those, so I suppose the same number is going to hit us today. Couldn't the parties interested in those mails either just check the web page or create a separate mailing list? Regards -- ^TM - 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 (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10762&projectId=83 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 16:02:27 + Finished at: Tue 2 Aug 2011 16:04:04 + Total time: 1m 37s Build Trigger: Forced Build Number: 162 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 788 Failures: 0 Errors: 0 Success Rate: 100 Total time: 57.238018 - 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 FileUpload - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10760&projectId=81 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 16:01:43 + Finished at: Tue 2 Aug 2011 16:02:01 + Total time: 18s Build Trigger: Forced Build Number: 8 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 33 Failures: 0 Errors: 0 Success Rate: 100 Total time: 5.614 - 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 EL - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10757&projectId=78 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 15:59:50 + Finished at: Tue 2 Aug 2011 16:00:00 + Total time: 10s Build Trigger: Forced Build Number: 5 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 4 Failures: 0 Errors: 0 Success Rate: 100 Total time: 0.096 - 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 Discovery - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10756&projectId=76 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 15:59:33 + Finished at: Tue 2 Aug 2011 15:59:49 + Total time: 16s Build Trigger: Forced Build Number: 48 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 14 Failures: 0 Errors: 0 Success Rate: 100 Total time: 0.128 - 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 DbUtils - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10754&projectId=74 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 15:59:04 + Finished at: Tue 2 Aug 2011 15:59:15 + Total time: 10s Build Trigger: Forced Build Number: 10 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 91 Failures: 0 Errors: 0 Success Rate: 100 Total time: 0.8916 - 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 Configuration - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10751&projectId=72 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 15:49:46 + Finished at: Tue 2 Aug 2011 15:51:07 + Total time: 1m 21s Build Trigger: Forced Build Number: 37 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 1518 Failures: 0 Errors: 0 Success Rate: 100 Total time: 60.038 - 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 Collections - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10750&projectId=71 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 15:48:57 + Finished at: Tue 2 Aug 2011 15:49:42 + Total time: 45s Build Trigger: Forced Build Number: 43 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 11577 Failures: 0 Errors: 0 Success Rate: 100 Total time: 22.27 - 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 Codec - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10749&projectId=70 Build statistics: State: Failed Previous State: Failed Started at: Tue 2 Aug 2011 15:48:25 + Finished at: Tue 2 Aug 2011 15:48:55 + Total time: 29s Build Trigger: Forced Build Number: 107 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 409 Failures: 0 Errors: 0 Success Rate: 100 Total time: 15.812 - 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 Chain - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10748&projectId=69 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 15:48:12 + Finished at: Tue 2 Aug 2011 15:48:24 + Total time: 11s Build Trigger: Forced Build Number: 9 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 116 Failures: 0 Errors: 0 Success Rate: 100 Total time: 0.8246 - 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 CLI - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10746&projectId=67 Build statistics: State: Failed Previous State: Failed Started at: Tue 2 Aug 2011 15:47:50 + Finished at: Tue 2 Aug 2011 15:48:00 + Total time: 10s Build Trigger: Forced Build Number: 23 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 361 Failures: 0 Errors: 0 Success Rate: 100 Total time: 0.285 - 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 BeanUtils - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10745&projectId=65 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 15:46:35 + Finished at: Tue 2 Aug 2011 15:47:48 + Total time: 1m 12s Build Trigger: Forced Build Number: 6 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 1181 Failures: 0 Errors: 0 Success Rate: 100 Total time: 24.327002 - 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 CLI - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10742&projectId=67 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 15:42:31 + Finished at: Tue 2 Aug 2011 15:42:43 + Total time: 12s Build Trigger: Forced Build Number: 23 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy 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: 361 Failures: 0 Errors: 0 Success Rate: 100 Total time: 0.326 - 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 CLI - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10740&projectId=67 Build statistics: State: Failed Previous State: Failed Started at: Tue 2 Aug 2011 15:13:58 + Finished at: Tue 2 Aug 2011 15:14:22 + Total time: 23s Build Trigger: Forced Build Number: 22 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean install deploy 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: 361 Failures: 0 Errors: 0 Success Rate: 100 Total time: 0.7410001 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[continuum] BUILD FAILURE: Apache Commons - Apache Commons Digester - Default Maven 2 Build Definition (Java 1.5)
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10739&projectId=75 Build statistics: State: Failed Previous State: Ok Started at: Tue 2 Aug 2011 15:13:08 + Finished at: Tue 2 Aug 2011 15:13:51 + Total time: 42s Build Trigger: Forced Build Number: 93 Exit code: 1 Building machine hostname: vmbuild Operating system : Linux(unknown) Java Home version : java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix" SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean install deploy 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: 182 Failures: 0 Errors: 0 Success Rate: 100 Total time: 3.578 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Nexus vs rsync-repository releases
On 2 August 2011 15:29, Mark Thomas wrote: > On 02/08/2011 15:23, Emmanuel Bourg wrote: >> Are we still going to deploy Maven artifacts by SCPing to >> m2-ibiblio-rsync-repository on people.apache.org? >> >> I've been discussing the permissions issue for the old groupIds on Nexus >> with the Infra team (i.e components using the old groupId >> commons- need a specific configuration on the snapshot >> and release repositories). >> >> Brian Demers kindly proposed to allow the deployment of all commons-* >> groups on Nexus, but it would require to block the deployment through >> people.apache.org to avoid metadata conflicts. >> >> Do we all agree on using exclusively Nexus for our releases? > > What benefits do we get by using Nexus and what extra hoops do we have > to jump through to get them compared to just using scp? The benefits are: * metadata is automatically updated * intercepts all uploads, so cannot accidentally deploy to live repo * automatically checks that signing keys are publicly available * ensures that the artifacts voted on are the ones actually deployed Nexus is automatically used if the gid is o.a.commons. One just has to use "mvn deploy" and the artifacts will be uploaded to the staging area. The extra steps that have to be done are: 1) Close the staging repo once all the artifacts have been uploaded. This makes the staging area visible for release votes. 2a) Publish the staging repo once the release vote has passed. This allows the artifacts to propagate to Maven Central. OR 2b) Drop the staged artifacts, and re-roll the release. > 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: Nexus vs rsync-repository releases
On 02/08/2011 15:23, Emmanuel Bourg wrote: > Are we still going to deploy Maven artifacts by SCPing to > m2-ibiblio-rsync-repository on people.apache.org? > > I've been discussing the permissions issue for the old groupIds on Nexus > with the Infra team (i.e components using the old groupId > commons- need a specific configuration on the snapshot > and release repositories). > > Brian Demers kindly proposed to allow the deployment of all commons-* > groups on Nexus, but it would require to block the deployment through > people.apache.org to avoid metadata conflicts. > > Do we all agree on using exclusively Nexus for our releases? What benefits do we get by using Nexus and what extra hoops do we have to jump through to get them compared to just using scp? Mark - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Nexus vs rsync-repository releases
Are we still going to deploy Maven artifacts by SCPing to m2-ibiblio-rsync-repository on people.apache.org? I've been discussing the permissions issue for the old groupIds on Nexus with the Infra team (i.e components using the old groupId commons- need a specific configuration on the snapshot and release repositories). Brian Demers kindly proposed to allow the deployment of all commons-* groups on Nexus, but it would require to block the deployment through people.apache.org to avoid metadata conflicts. Do we all agree on using exclusively Nexus for our releases? Emmanuel Bourg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[compress] Deflater#getBytesRead and friends
Hi, one of the main drivers for switching to Java5 was that the methods you use to determine the compressed and uncompressed sizes of data for ZIP archives used to return ints in Java 1.4 and new methods have been added that return longs. I've committed an ignored unit test inside the ZIP package (DeflaterInflaterTest) that shows that those methods really only return unsigned ints and not longs for any JDK < 7 that I have tested so far. The tests compress 4GByte + 4KByte of data and the methods return 4KByte when asked how many bytes they have seen. ZipArchiveOutputStream has already been changed to count the bytes itself and not rely on Deflater, but only for the uncompressed size. I'm afraid the same "unsigned int" behavior applies to the methods returning the compressed sizes as well but I don't have the patience to wait for Deflater to eat up enough random data so that the compressed result finally exceeds 4GByte (the existing test case already takes four minutes on my personal notebook - less than two at work, time to invest, maybe). ZipArchiveOutputStream can intercept the stream and simply count how many bytes have been written to determine the compressed size, but ZipArchiveInputStream is a different beast. It may be a useful heuristic to assume that the result is correct modulo 2^32. ZipArchiveInputStream knows how many bytes it has read but it might have read more than it needed to and has to push back the excess bytes when decompressing a file. It knows the compressed size must be between the number of bytes read and the number of bytes read before the last read operation so the offset in multiples of 4GByte that is missing for the remainder could be determined. For this heuristic to work we'd need to be sure the value returned by Inflater is either correct or correct modulo 2^32 and I'd ask anybody with a more exotic Java impl than I have used (OpenJDK on Linux, Sun/Oracle versions of Java5/6/7 on Win7) to remove the @Ignore from the test case and run it. It should either pass or return something like Failed tests: deflaterBytesRead(org.apache.commons.compress.archivers.zip.DeflaterInflaterTest): expected:<4294971392> but was:<4096> inflaterBytesWritten(org.apache.commons.compress.archivers.zip.DeflaterInflaterTest): expected:<4294971392> but was:<4096> Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE][DAEMON] Release Apache Commons Daemon 1.0.7
- Mail original - > The proposed Apache Commons Daemon 1.0.7 release is now available for > voting. > > It can be obtained from: > http://people.apache.org/~mturk/daemon-1.0.7/ > The svn tag is: > https://svn.apache.org/repos/asf/commons/proper/daemon/tags/COMMONS_DAEMON_1_0_7_RC1/ > > The vote will last for 72 hours or less if enough votes are > collected. > As usual, if voted, the tag will be renamed to COMMONS_DAEMON_1_0_7. > > > The proposed 1.0.7 release is: > [ ] Stable - go ahead and release as 1.0.7 Stable > [ ] Broken - do not release +1 (for Linux part, I don't have access to any Windows machine) Luc > > > Regards > -- > ^TM > > - > 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-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 12 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: 14 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.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.029 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.013 sec Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 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.03 sec Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.163 sec Running org.apache.commons.proxy.exception.TestProxyFactoryException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 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.022 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: 13 seconds [INFO] Finished at: Tue Aug 02 11:29:33 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.or
Re: [VOTE][DAEMON] Release Apache Commons Daemon 1.0.7
On Tue, Aug 2, 2011 at 8:29 AM, Phil Steitz wrote: > On 8/1/11 11:23 PM, Henri Yandell wrote: >> svn list https://svn.apache.org/repos/private/committers/tools/releases >> >> compare_dirs.pl grab_releases.sh >> sign_and_hash.sh verify_archive_equivalence.sh >> gpg-sign-all multisign.sh symlinks.sh >> verify_sigs.sh >> >> Various scripts. I suspect some do the same thing :) > > Yep. I used verify_sigs to verify the hashes and sigs on this one > and grab_releases to download it :) You can work for years at the ASF and still find jewels like that in some dark corners ;-) Actually grab_releases is a missing feature in my script Cheers! > > Phil >> >> Hen >> >> On Mon, Aug 1, 2011 at 10:45 PM, Simone Tripodi >> wrote: >>> +1 >>> >>> I additionally used a shell script (kindly provided on Christian >>> Grobmeier blog[1]) to check signatures and output is OK >>> Well done!!! >>> Have a nice day, all the best, >>> Simo >>> >>> [1] >>> http://www.grobmeier.de/checking-md5-and-signatures-with-a-shell-script-29062011.html >>> >>> $ ./verify.sh >>> Checking file: ./commons-daemon-1.0.7.jar >>> Using md5 file: ./commons-daemon-1.0.7.jar.md5 >>> c3460b191a233c8ed4f7bd041a3b3cdf >>> c3460b191a233c8ed4f7bd041a3b3cdf >>> md5 checksums OK >>> Checking file: ./commons-daemon-1.0.7.jar >>> Using sha1 file: ./commons-daemon-1.0.7.jar.sha1 >>> 6177d189e62ac37bf136b6a35fd3ff4a5e8a183a >>> 6177d189e62ac37bf136b6a35fd3ff4a5e8a183a >>> sha1 checksums OK >>> GPG verification output >>> gpg: Signature made Tue Aug 2 06:51:18 2011 CEST using DSA key ID 564C17A3 >>> gpg: Good signature from "Mladen Turk (*** DEFAULT SIGNING KEY ***) >>> " >>> gpg: WARNING: This key is not certified with a trusted signature! >>> gpg: There is no indication that the signature belongs to the >>> owner. >>> Primary key fingerprint: 61B8 32AC 2F1C 5A90 F0F9 B00A 1C50 6407 564C 17A3 >>> ~~~ >>> Checking file: ./commons-daemon-1.0.7-bin.tar.gz >>> Using md5 file: ./commons-daemon-1.0.7-bin.tar.gz.md5 >>> b31ff577b101420d780271a7b055eab5 >>> b31ff577b101420d780271a7b055eab5 >>> md5 checksums OK >>> Checking file: ./commons-daemon-1.0.7-bin.tar.gz >>> Using sha1 file: ./commons-daemon-1.0.7-bin.tar.gz.sha1 >>> ce5a26078e77ea38f53169f3938872c3d76e0a6e >>> ce5a26078e77ea38f53169f3938872c3d76e0a6e >>> sha1 checksums OK >>> GPG verification output >>> gpg: Signature made Tue Aug 2 06:51:32 2011 CEST using DSA key ID 564C17A3 >>> gpg: Good signature from "Mladen Turk (*** DEFAULT SIGNING KEY ***) >>> " >>> gpg: WARNING: This key is not certified with a trusted signature! >>> gpg: There is no indication that the signature belongs to the >>> owner. >>> Primary key fingerprint: 61B8 32AC 2F1C 5A90 F0F9 B00A 1C50 6407 564C 17A3 >>> ~~~ >>> Checking file: ./commons-daemon-1.0.7-bin.zip >>> Using md5 file: ./commons-daemon-1.0.7-bin.zip.md5 >>> 8b978ce01ffac6eab97250df4cb528da >>> 8b978ce01ffac6eab97250df4cb528da >>> md5 checksums OK >>> Checking file: ./commons-daemon-1.0.7-bin.zip >>> Using sha1 file: ./commons-daemon-1.0.7-bin.zip.sha1 >>> 060bc3ce907522f58baf8a841865c41c8a3c0e25 >>> 060bc3ce907522f58baf8a841865c41c8a3c0e25 >>> sha1 checksums OK >>> GPG verification output >>> gpg: Signature made Tue Aug 2 06:51:03 2011 CEST using DSA key ID 564C17A3 >>> gpg: Good signature from "Mladen Turk (*** DEFAULT SIGNING KEY ***) >>> " >>> gpg: WARNING: This key is not certified with a trusted signature! >>> gpg: There is no indication that the signature belongs to the >>> owner. >>> Primary key fingerprint: 61B8 32AC 2F1C 5A90 F0F9 B00A 1C50 6407 564C 17A3 >>> >>> http://people.apache.org/~simonetripodi/ >>> http://www.99soft.org/ >>> >>> >>> >>> On Tue, Aug 2, 2011 at 7:28 AM, Phil Steitz wrote: +1 Phil On 8/1/11 10:06 PM, Mladen Turk wrote: > The proposed Apache Commons Daemon 1.0.7 release is now available > for voting. > > It can be obtained from: > http://people.apache.org/~mturk/daemon-1.0.7/ > The svn tag is: > https://svn.apache.org/repos/asf/commons/proper/daemon/tags/COMMONS_DAEMON_1_0_7_RC1/ > > > The vote will last for 72 hours or less if enough votes are > collected. > As usual, if voted, the tag will be renamed to COMMONS_DAEMON_1_0_7. > > > The proposed 1.0.7 release is: > [ ] Stable - go ahead and release as 1.0.7 Stable > [ ] Broken - do not release > > > Regards - 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
Re: [VOTE][DAEMON] Release Apache Commons Daemon 1.0.7
+1 Thanks Mladen! On Tue, Aug 2, 2011 at 7:06 AM, Mladen Turk wrote: > The proposed Apache Commons Daemon 1.0.7 release is now available for > voting. > > It can be obtained from: > http://people.apache.org/~mturk/daemon-1.0.7/ > The svn tag is: > https://svn.apache.org/repos/asf/commons/proper/daemon/tags/COMMONS_DAEMON_1_0_7_RC1/ > > The vote will last for 72 hours or less if enough votes are collected. > As usual, if voted, the tag will be renamed to COMMONS_DAEMON_1_0_7. > > > The proposed 1.0.7 release is: > [ ] Stable - go ahead and release as 1.0.7 Stable > [ ] Broken - do not release > > > Regards > -- > ^TM > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- http://www.grobmeier.de - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE][DAEMON] Release Apache Commons Daemon 1.0.7
On 2011-08-02, Mladen Turk wrote: > http://people.apache.org/~mturk/daemon-1.0.7/ > The svn tag is: > https://svn.apache.org/repos/asf/commons/proper/daemon/tags/COMMONS_DAEMON_1_0_7_RC1/ > The proposed 1.0.7 release is: > [ ] Stable - go ahead and release as 1.0.7 Stable > [ ] Broken - do not release No functional tests from my side, but checked hashes and sigs, RAT is happy, NOTICE and LICENSE look good. The only diffs between the combined source downloads and the tag I found were due to different line ends and svn keyword expansions. Don't know whether it is stable but +1, go ahead and release it. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
RE: [math] Adding a new class to handle Matrix with 3 columns/rows
> >> For very big matrix (ie : beyond 500 or 1000 rows/columns), the >> computation is faster if you transpose the second matrix and then >> multiply. The two inner loops are inversed and it allows a significant >> gain for very big matrix (about 40% compared to Commons Math for >> 1000x1000 matrix, and 50% compared to the classical triple loop). I >> guess that it's faster for the JVM to access the matrix coefficients >> in the computer's memory. > >For large matrices, did you compare with BlockRealMatrix ? It was specially designed to improve caching. This is the >>reason why when you build a matrix using the various factory methods MatrixUtils.createRealMatrix (or createFieldMatrix), there is a test about the dimension and either an Array2DRowRealMatrix or a BlockRealMatrix is created. The current threshold has been set to 4096 elements, but this was an almost arbitrary choice. >best regards, >Luc You are right, BlockRealMatrix is even more efficient : 4x faster than our implementation, and 6x faster than the Array2DRowRealMatrix for big Matrix... Yannick - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [logging] logging vs slf4j
Le 28/07/2011 22:01, Henri Yandell a écrit : Personally I'm happy for commons-logging to die. :) Yeah let's use java.util.logging instead :) Emmanuel Bourg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Nightly snapshots
I've done some tests of snapshot deployment, here are my observations: - Continuum is not properly configured to deploy Maven snapshots. If we want to use it we'll have to request some help from the infra team. - Snapshots for several projects using the old groupId commons-* can't be deployed, it requires a change in the Nexus configuration. These projects are beanutils, chain, cli, collections, configuration, dbutils, io, jxpath, scxml, validator. - JCS is still deployed on the org.apache.jcs group. Commons developer accounts are not allowed to deploy it. Emmanuel Bourg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [LANG] Proposing 3.0.1
Here's a generated site: http://people.apache.org/~bayard/commons-lang-3.0.1-SNAPSHOT-site/ Review the additions in the clirr report. Note the checkstyle and findbugs reports have items that need cleanup prior to release. Hen On Tue, Aug 2, 2011 at 12:27 AM, Henri Yandell wrote: > I'd like to release 3.0.1 of Lang. It would contain the following 11 fixes: > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+LANG+AND+fixVersion+%3D+%223.0.1%22+AND+resolution+in+%28Fixed%2C+%22Won%27t+Fix%22%2C+Duplicate%2C+Invalid%2C+Incomplete%2C+%22Cannot+Reproduce%22%2C+Later%2C+%22Not+A+Problem%22%2C+Unresolved%29 > > LANG-611 Consider improvements in LANG-396 > LANG-626 object cloning with SerializationUtils has classloader > problems with no workaround > LANG-708 StringEscapeUtils.escapeEcmaScript from lang3 cuts off long > unicode string > LANG-717 Specify source encoding for build > LANG-720 StringEscapeUtils.escapeXml(input) outputs wrong results > when an input contains characters in Supplementary Planes. > LANG-721 Complement ArrayUtils.addAll() variants with by-index and > by-value removal methods > LANG-722 Add BooleanUtils.and/or varargs methods to complement xor > LANG-723 Add mode and median Comparable... methods to ObjectUtils > LANG-726 Add a method e.g. Range Range.intersectionWith(Range) > LANG-727 ToStringBuilderTest.testReflectionHierarchyArrayList fails > with IBM JDK 6 > LANG-730 EnumSet -> BitVector > > Two issues were pushed back to 3.0.2 as 'not ready', and there are 54 > items in 3.x for consideration. > > The biggest issue needing feedback would (imo) be LANG-626. > > I'll get a clirr report put together (and update the site); for now > use this thread if you have any objections to a 3.0.1 release. > > Hen > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [LANG] Proposing 3.0.1
Hi Hen, Henri Yandell wrote: > I'd like to release 3.0.1 of Lang. It would contain the following 11 > fixes: > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+LANG+AND+fixVersion+%3D+%223.0.1%22+AND+resolution+in+%28Fixed%2C+%22Won%27t+Fix%22%2C+Duplicate%2C+Invalid%2C+Incomplete%2C+%22Cannot+Reproduce%22%2C+Later%2C+%22Not+A+Problem%22%2C+Unresolved%29 > > LANG-611 Consider improvements in LANG-396 > LANG-626 object cloning with SerializationUtils has classloader > problems with no workaround > LANG-708 StringEscapeUtils.escapeEcmaScript from lang3 cuts off long > unicode string > LANG-717 Specify source encoding for build > LANG-720 StringEscapeUtils.escapeXml(input) outputs wrong results > when an input contains characters in Supplementary Planes. > LANG-721 Complement ArrayUtils.addAll() variants with by-index and > by-value removal methods > LANG-722 Add BooleanUtils.and/or varargs methods to complement xor > LANG-723 Add mode and median Comparable... methods to ObjectUtils > LANG-726 Add a method e.g. Range Range.intersectionWith(Range) > LANG-727 ToStringBuilderTest.testReflectionHierarchyArrayList fails > with IBM JDK 6 > LANG-730 EnumSet -> BitVector > > Two issues were pushed back to 3.0.2 as 'not ready', and there are 54 > items in 3.x for consideration. > > The biggest issue needing feedback would (imo) be LANG-626. > > I'll get a clirr report put together (and update the site); for now > use this thread if you have any objections to a 3.0.1 release. I'd like to add first a getRawMessage() calling super.getMessage() to Contexted(Runtime)Exception as counter part to the getFormattedExceptionMessage(). I'll do it this evening. Cheers, Jörg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[LANG] Proposing 3.0.1
I'd like to release 3.0.1 of Lang. It would contain the following 11 fixes: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+LANG+AND+fixVersion+%3D+%223.0.1%22+AND+resolution+in+%28Fixed%2C+%22Won%27t+Fix%22%2C+Duplicate%2C+Invalid%2C+Incomplete%2C+%22Cannot+Reproduce%22%2C+Later%2C+%22Not+A+Problem%22%2C+Unresolved%29 LANG-611Consider improvements in LANG-396 LANG-626object cloning with SerializationUtils has classloader problems with no workaround LANG-708StringEscapeUtils.escapeEcmaScript from lang3 cuts off long unicode string LANG-717Specify source encoding for build LANG-720StringEscapeUtils.escapeXml(input) outputs wrong results when an input contains characters in Supplementary Planes. LANG-721Complement ArrayUtils.addAll() variants with by-index and by-value removal methods LANG-722Add BooleanUtils.and/or varargs methods to complement xor LANG-723Add mode and median Comparable... methods to ObjectUtils LANG-726Add a method e.g. Range Range.intersectionWith(Range) LANG-727ToStringBuilderTest.testReflectionHierarchyArrayList fails with IBM JDK 6 LANG-730EnumSet -> BitVector Two issues were pushed back to 3.0.2 as 'not ready', and there are 54 items in 3.x for consideration. The biggest issue needing feedback would (imo) be LANG-626. I'll get a clirr report put together (and update the site); for now use this thread if you have any objections to a 3.0.1 release. Hen - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [lang] LANG-686 Recursive call of replaceEachRepeatedly
On Sat, Jul 30, 2011 at 2:27 AM, Henri Yandell wrote: > On Fri, Jul 29, 2011 at 8:27 AM, Gary Gregory wrote: >> Hi Hen, >> >> I am not really comfortable knowing that a SOE can be a "normal" code >> path. It would have to be Javadoc'd to boot. >> >> I can see catching IllegalStateException and IllegalArgumentException >> in client code, especially in a server or a processor of some kind, >> but to do that for SOE feels wrong. An SOE would crash a server based >> a client request for example. > > Any thoughts on how to define an arbitrary number of loops to allow? > Throwing an ISE (or IAE) to protect against SOE when it's a loop of 2 > is a bit aggressive :) > >> I think I'd rather keep the exception. Also I think it should be an >> IAE instead of an ISE because the problem is that the arguments are >> bad and the SU class does have state. > > I think it used to be an IAE. The javadoc definitely was. > > Easy to change back. Looking at the history of the code, I think it's always been an ISE with an IAE listed in the javadoc. Additionally array lengths have thrown an IAE and declared a IndexOutOfBoundsException. Lovely :) For now my intention is to fix the javadoc and improve the exception method and discuss other changes later. Hen - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
