Build failed in Jenkins: Commons-Compress-Windows #123

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #122

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #121

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #120

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Fwd: Build failed in Jenkins: Commons-Compress-Windows #119

Does anyone know how to fix this? Gary -- Forwarded message -- From: Apache Jenkins Server Date: Wed, Jan 4, 2017 at 7:21 PM Subject: Build failed in Jenkins: Commons-Compress-Windows #119 To: dev@commons.apache.org See

Build failed in Jenkins: Commons-Compress-Windows #119

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #118

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #117

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #116

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #115

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #114

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #113

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #112

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #111

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #110

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #109

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #108

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Re: [commons-complex] Pushing Apache git repo to Github mirror

On Wed, 04 Jan 2017 16:16:53 +0100, Stefan Bodewig wrote: On 2017-01-04, Eric Barnhill wrote: I have read the information regarding read-only git mirrors at http://apache.org/dev/git.html . You are not using a read-only mirror for [complex], so http://www.apache.org/dev/writable-git applies.

Re: [commons-complex] Pushing Apache git repo to Github mirror

On 2017-01-04, Eric Barnhill wrote: > I have read the information regarding read-only git mirrors at > http://apache.org/dev/git.html . You are not using a read-only mirror for [complex], so http://www.apache.org/dev/writable-git applies. Not that it'd say too much or help in a particular way

Build failed in Jenkins: Commons-Compress-Windows #107

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

[complex] Re: First commit to commons-complex git page

Hi Eric. On Wed, 4 Jan 2017 11:14:40 +0100, Eric Barnhill wrote: To enable others to work on the code, I have posted the first commit to commons-complex. Thanks. Please note that the code compiles but does not yet pass mvn test. This is what I am working on right now. Between replacing

[commons-complex] Pushing Apache git repo to Github mirror

I have read the information regarding read-only git mirrors at http://apache.org/dev/git.html . However I have a git mirror for commons-complex at https://github.com/apache/commons-complex , it is empty while the apache git repo at https://git-wip-us.apache.org/repos/asf?p=commons-complex.git has

Build failed in Jenkins: Commons-Compress-Windows #106

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Re: [ALL] how to move a project out of the sandbox?

On 4 January 2017 at 13:16, Emmanuel Bourg wrote: > Le 4/01/2017 à 12:58, sebb a écrit : > >> That was done originally, but then the same name space is used for >> common pages as for component names. >> >> e.g. there could not be common pages called resources.html and

Re: [VOTE] Promote TEXT to Proper

Le 4/01/2017 à 11:11, Thomas Vandahl a écrit : > Would it be possible to check generally available code bases for usage > statistics of the commons libraries classes? We could derive some > packaging hints from this information. I'd argue that many people use > commons-lang just for StringUtils,

Re: [VOTE] Promote TEXT to Proper

+1 Emmanuel Bourg Le 3/01/2017 à 20:39, Rob Tompkins a écrit : > Hello all, > > I propose that we move [text] to Commons Proper. > > -- > [ ] +1 Move [text] to Commons Proper > [ ] +0 I am fine with this move > [ ] -0 I am not

Build failed in Jenkins: Commons-Compress-Windows #105

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Re: [ALL] how to move a project out of the sandbox?

Le 4/01/2017 à 12:58, sebb a écrit : > That was done originally, but then the same name space is used for > common pages as for component names. > > e.g. there could not be common pages called resources.html and email.html. Why not? An email.html file could co-exist with an email/ directory

Build failed in Jenkins: Commons-Compress-Windows #104

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Re: [ALL] how to move a project out of the sandbox?

On 4 January 2017 at 08:30, Emmanuel Bourg wrote: > Le 4/01/2017 à 01:27, sebb a écrit : >> Where do pre-release components appear on the website? > > I'd suggest flattening the layout of the site and putting all components > at the same level (proper, sandbox, dormant): > >

Build failed in Jenkins: Commons-Compress-Windows #103

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Build failed in Jenkins: Commons-Compress-Windows #102

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Re: [ALL] how to move a project out of the sandbox?

Le 4/01/2017 à 01:44, Gilles a écrit : > Alternative would be that any committer is allowed to ask INFRA > to create a git repository. Is it that which you advocate for? Assuming there is a consensus to do so, yes. But if a committer just wants to play alone in a corner he can do it on GitHub,

First commit to commons-complex git page

To enable others to work on the code, I have posted the first commit to commons-complex. Please note that the code compiles but does not yet pass mvn test. This is what I am working on right now. Between replacing Precision.equals() type methods with private local equals() methods for each

Re: [VOTE] Promote TEXT to Proper

On 03.01.17 20:39, Rob Tompkins wrote: > Hello all, > > I propose that we move [text] to Commons Proper. > > -- > [X] +1 Move [text] to Commons Proper > [ ] +0 I am fine with this move > [ ] -0 I am not too keen, because ... > [ ]

Build failed in Jenkins: Commons-Compress-Windows #101

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace

Re: [VOTE] Promote TEXT to Proper

+1 (non-binding) > On 4 Jan 2017, at 06:46, Benedikt Ritter wrote: > > Hello Rob, > > Rob Tompkins schrieb am Di., 3. Jan. 2017 um 20:40 Uhr: > >> Hello all, >> >> I propose that we move [text] to Commons Proper. >> >>

Re: [ALL] how to move a project out of the sandbox?

Le 4/01/2017 à 01:27, sebb a écrit : > Where do pre-release components appear on the website? I'd suggest flattening the layout of the site and putting all components at the same level (proper, sandbox, dormant): http://commons.apache.org/foo/ http://commons.apache.org/bar/ instead of:

Build failed in Jenkins: Commons-Compress-Windows #100

See -- [...truncated 8 lines...] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1695) at