Re: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-09 Thread Benedikt Ritter 
Hello Paul,

> Am 10.03.2017 um 01:03 schrieb Paul King :
> 
> Oh, I did notice that the README.md still has 1.3.1 rather than 1.4
> when referencing
> how to retrieve the Maven artifact. Is a "mvn commons:readme-md" required?

You’re right, it would be better to have this correct in the release tag. 
However I usually update the README.md after the artifacts have been published, 
because the README.md will directly be visible on GitHub. I don’t want to 
confuse users looking for coordinates on GitHub. Since CLI is still on SVN and 
I don’t do release branches in SVN I have to make all release preparations on 
trunk/master.

Thanks for reviewing!
Benedikt

> 
> On Fri, Mar 10, 2017 at 10:00 AM, Paul King  wrote:
>> +1 (non-binding)
>> I checked md5/sha1/asc for the sources jar and src zip.
>> I ran "mvn test" from the src zip using Java 1.6.0_45 and Maven 3.2.5.
>> I ran Apache Groovy's test suite against 1.4 which runs quite a few
>> tests for CliBuilder (which has commons cli under the covers) as well
>> as numerous other tests where Groovy uses commons cli directly too.
>> 
>> Cheers, Paul.
>> 
>> 
>> On Thu, Mar 9, 2017 at 11:30 PM, Benedikt Ritter  wrote:
>>> Hi,
>>> 
>>> We have fixed some bugs and added two new features since CLI 1.3.1 was 
>>> released,
>>> so I would like to release CLI 1.4.
>>> 
>>> CLI 1.4 RC1 is available for review here:
>>>https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
>>> revision 18640)
>>> 
>>> The tag is here:
>>>http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ 
>>> (svn revision 1786159)
>>>N.B. the SVN revision is required because SVN tags are not immutable.
>>> 
>>> Maven artifacts are here:
>>>  https://repository.apache.org/content/repositories/orgapachecommons-1240
>>> 
>>> These are the Maven Artifacts and their hashes:
>>> 
>>> commons-cli-1.4.pom.asc
>>> (SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
>>> commons-cli-1.4-test-sources.jar
>>> (SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
>>> commons-cli-1.4.jar
>>> (SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
>>> commons-cli-1.4-sources.jar.asc
>>> (SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
>>> commons-cli-1.4-tests.jar
>>> (SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
>>> commons-cli-1.4-tests.jar.asc
>>> (SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
>>> commons-cli-1.4-javadoc.jar.asc
>>> (SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
>>> commons-cli-1.4-sources.jar
>>> (SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
>>> commons-cli-1.4-javadoc.jar
>>> (SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
>>> commons-cli-1.4-test-sources.jar.asc
>>> (SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
>>> commons-cli-1.4.jar.asc
>>> (SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
>>> commons-cli-1.4.pom
>>> (SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)
>>> 
>>> I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that 
>>> CLI required at least Java 5 and I haven’t tested this release with 1.5 or 
>>> 1.6. If anybody has such old JDKs installed, I would appreciate some 
>>> feedback on this.
>>> 
>>> Details of changes since 1.3.1 are in the release notes:
>>>  
>>> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
>>>  http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html
>>> 
>>> Site:
>>>  http://home.apache.org/~britter/commons/cli/1.4-RC1/
>>>  (note some *relative* links are broken and the 1.4 directories are not yet 
>>> created - these will be OK once the site is deployed)
>>> 
>>> Clirr Report (compared to 1.3.1):
>>>  http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
>>> (Sorry, after updating to commons-parent 42 the clirr report was not 
>>> generated anymore. I had to do it by hand, that’s why it has a different 
>>> style)
>>> 
>>> RAT Report:
>>>  http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html
>>> 
>>> KEYS:
>>>  https://www.apache.org/dist/commons/KEYS
>>> 
>>> Please review the release candidate and vote.
>>> This vote will close no sooner that 72 hours from now,
>>> i.e. sometime after 13:30 UTC 12-March 2017
>>> 
>>>  [ ] +1 Release these artifacts
>>>  [ ] +0 OK, but...
>>>  [ ] -0 OK, but really should fix...
>>>  [ ] -1 I oppose this release because...
>>> 
>>> Thanks!
>>> 
>>> Benedikt
>>> 
>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For

Re: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-09 Thread Bruno P. Kinoshita 
[ X ] +1 Release these artifacts

Builds fine on

Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_NZ, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-64-generic", arch: "amd64", family: "unix"

Site successfully generated too, no outstanding issues in the reports.

Cheers
Bruno




- Original Message -
From: Benedikt Ritter 
To: Commons Developers List 
Cc: Robert Scholte 
Sent: Friday, 10 March 2017 2:30 AM
Subject: [VOTE] Release Apache Commons CLI 1.4 based on RC1

Hi,

We have fixed some bugs and added two new features since CLI 1.3.1 was released,
so I would like to release CLI 1.4.

CLI 1.4 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
revision 18640)

The tag is here:
http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ (svn 
revision 1786159)
N.B. the SVN revision is required because SVN tags are not immutable.

Maven artifacts are here:
  https://repository.apache.org/content/repositories/orgapachecommons-1240

These are the Maven Artifacts and their hashes:

commons-cli-1.4.pom.asc
(SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
commons-cli-1.4-test-sources.jar
(SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
commons-cli-1.4.jar
(SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
commons-cli-1.4-sources.jar.asc
(SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
commons-cli-1.4-tests.jar
(SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
commons-cli-1.4-tests.jar.asc
(SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
commons-cli-1.4-javadoc.jar.asc
(SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
commons-cli-1.4-sources.jar
(SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
commons-cli-1.4-javadoc.jar
(SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
commons-cli-1.4-test-sources.jar.asc
(SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
commons-cli-1.4.jar.asc
(SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
commons-cli-1.4.pom
(SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)

I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that CLI 
required at least Java 5 and I haven’t tested this release with 1.5 or 1.6. If 
anybody has such old JDKs installed, I would appreciate some feedback on this.

Details of changes since 1.3.1 are in the release notes:
  
https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
  http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html

Site:
  http://home.apache.org/~britter/commons/cli/1.4-RC1/
  (note some *relative* links are broken and the 1.4 directories are not yet 
created - these will be OK once the site is deployed)

Clirr Report (compared to 1.3.1):
  http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
(Sorry, after updating to commons-parent 42 the clirr report was not generated 
anymore. I had to do it by hand, that’s why it has a different style)

RAT Report:
  http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html

KEYS:
  https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner that 72 hours from now,
i.e. sometime after 13:30 UTC 12-March 2017

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

Thanks!

Benedikt




-
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: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-09 Thread Paul King 
Oh, I did notice that the README.md still has 1.3.1 rather than 1.4
when referencing
how to retrieve the Maven artifact. Is a "mvn commons:readme-md" required?

On Fri, Mar 10, 2017 at 10:00 AM, Paul King  wrote:
> +1 (non-binding)
> I checked md5/sha1/asc for the sources jar and src zip.
> I ran "mvn test" from the src zip using Java 1.6.0_45 and Maven 3.2.5.
> I ran Apache Groovy's test suite against 1.4 which runs quite a few
> tests for CliBuilder (which has commons cli under the covers) as well
> as numerous other tests where Groovy uses commons cli directly too.
>
> Cheers, Paul.
>
>
> On Thu, Mar 9, 2017 at 11:30 PM, Benedikt Ritter  wrote:
>> Hi,
>>
>> We have fixed some bugs and added two new features since CLI 1.3.1 was 
>> released,
>> so I would like to release CLI 1.4.
>>
>> CLI 1.4 RC1 is available for review here:
>> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
>> revision 18640)
>>
>> The tag is here:
>> http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ 
>> (svn revision 1786159)
>> N.B. the SVN revision is required because SVN tags are not immutable.
>>
>> Maven artifacts are here:
>>   https://repository.apache.org/content/repositories/orgapachecommons-1240
>>
>> These are the Maven Artifacts and their hashes:
>>
>> commons-cli-1.4.pom.asc
>> (SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
>> commons-cli-1.4-test-sources.jar
>> (SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
>> commons-cli-1.4.jar
>> (SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
>> commons-cli-1.4-sources.jar.asc
>> (SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
>> commons-cli-1.4-tests.jar
>> (SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
>> commons-cli-1.4-tests.jar.asc
>> (SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
>> commons-cli-1.4-javadoc.jar.asc
>> (SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
>> commons-cli-1.4-sources.jar
>> (SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
>> commons-cli-1.4-javadoc.jar
>> (SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
>> commons-cli-1.4-test-sources.jar.asc
>> (SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
>> commons-cli-1.4.jar.asc
>> (SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
>> commons-cli-1.4.pom
>> (SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)
>>
>> I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that CLI 
>> required at least Java 5 and I haven’t tested this release with 1.5 or 1.6. 
>> If anybody has such old JDKs installed, I would appreciate some feedback on 
>> this.
>>
>> Details of changes since 1.3.1 are in the release notes:
>>   
>> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
>>   http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html
>>
>> Site:
>>   http://home.apache.org/~britter/commons/cli/1.4-RC1/
>>   (note some *relative* links are broken and the 1.4 directories are not yet 
>> created - these will be OK once the site is deployed)
>>
>> Clirr Report (compared to 1.3.1):
>>   http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
>> (Sorry, after updating to commons-parent 42 the clirr report was not 
>> generated anymore. I had to do it by hand, that’s why it has a different 
>> style)
>>
>> RAT Report:
>>   http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html
>>
>> KEYS:
>>   https://www.apache.org/dist/commons/KEYS
>>
>> Please review the release candidate and vote.
>> This vote will close no sooner that 72 hours from now,
>> i.e. sometime after 13:30 UTC 12-March 2017
>>
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>>
>> Thanks!
>>
>> Benedikt
>>
>>
>>
>>
>> -
>> 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: [VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-09 Thread Paul King 
+1 (non-binding)
I checked md5/sha1/asc for the sources jar and src zip.
I ran "mvn test" from the src zip using Java 1.6.0_45 and Maven 3.2.5.
I ran Apache Groovy's test suite against 1.4 which runs quite a few
tests for CliBuilder (which has commons cli under the covers) as well
as numerous other tests where Groovy uses commons cli directly too.

Cheers, Paul.


On Thu, Mar 9, 2017 at 11:30 PM, Benedikt Ritter  wrote:
> Hi,
>
> We have fixed some bugs and added two new features since CLI 1.3.1 was 
> released,
> so I would like to release CLI 1.4.
>
> CLI 1.4 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
> revision 18640)
>
> The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ (svn 
> revision 1786159)
> N.B. the SVN revision is required because SVN tags are not immutable.
>
> Maven artifacts are here:
>   https://repository.apache.org/content/repositories/orgapachecommons-1240
>
> These are the Maven Artifacts and their hashes:
>
> commons-cli-1.4.pom.asc
> (SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
> commons-cli-1.4-test-sources.jar
> (SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
> commons-cli-1.4.jar
> (SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
> commons-cli-1.4-sources.jar.asc
> (SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
> commons-cli-1.4-tests.jar
> (SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
> commons-cli-1.4-tests.jar.asc
> (SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
> commons-cli-1.4-javadoc.jar.asc
> (SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
> commons-cli-1.4-sources.jar
> (SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
> commons-cli-1.4-javadoc.jar
> (SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
> commons-cli-1.4-test-sources.jar.asc
> (SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
> commons-cli-1.4.jar.asc
> (SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
> commons-cli-1.4.pom
> (SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)
>
> I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that CLI 
> required at least Java 5 and I haven’t tested this release with 1.5 or 1.6. 
> If anybody has such old JDKs installed, I would appreciate some feedback on 
> this.
>
> Details of changes since 1.3.1 are in the release notes:
>   
> https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html
>
> Site:
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/
>   (note some *relative* links are broken and the 1.4 directories are not yet 
> created - these will be OK once the site is deployed)
>
> Clirr Report (compared to 1.3.1):
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
> (Sorry, after updating to commons-parent 42 the clirr report was not 
> generated anymore. I had to do it by hand, that’s why it has a different 
> style)
>
> RAT Report:
>   http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html
>
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 13:30 UTC 12-March 2017
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Thanks!
>
> Benedikt
>
>
>
>
> -
> 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: New git mirror created: commons-pool.git

2017-03-09 Thread Matt Sicker 
You can use "git svn rebase" to pull down any updates from svn since you
last imported by the way. I used to use git-svn when working with svn
projects here, but that's not a very easy way to perform release management.

On 9 March 2017 at 16:38, sebb  wrote:

> On 9 March 2017 at 21:24, Matt Sicker  wrote:
> > The steps are pretty straightforward now:
> >
> > 1. Do a lazy majority vote to make sure nobody has problems with the
> > migration.
> > 2. Create a new git repo via the reporeq webapp.
> > 3. Get the authors.txt file: https://git-wip-us.apache.org/authors.txt
>
> Warn devs not to commit to SVN
> Record the current SVN revision details
>
> > 4. Use git-svn to import the subversion repo (there are instructions
> > somewhere on how to do this so you don't have to scan the entire svn
> > history to find the first revision of that subdirectory).
>
> Double-check that SVN has not been changed since the start of the process
> If necessary, redo the conversion
>
> > 5. Push that converted repo to the newly created one.
>
> Rename SVN to https://svn.apache.org/repos/asf/commons/_moved_to_git/
> and leave text file behind, e.g. as per
>
> https://svn.apache.org/repos/asf/commons/proper/compress/
>
> Moving the SVN tree could be done earlier, to make it less likely that
> devs will accidentally commit.
>
> There will probably be some noise from CI jobs whilst the changes are
> made...
>
> > It's actually somewhat of a pain in the ass and is probably why infra
> made
> > it self-service. ;)
> >
> > On 9 March 2017 at 14:30, Oliver Heger 
> wrote:
> >
> >> Hi,
> >>
> >> Am 09.03.2017 um 15:58 schrieb Matt Sicker:
> >> > Thanks! I don't think I'll be able to convert the repo until tomorrow,
> >> > however.
> >>
> >> I would be interested to also move [configuration] to git, but - as
> >> usual - am pretty busy currently. Is there a documentation somewhere for
> >> the single steps that need to be done?
> >>
> >> Thanks
> >> Oliver
> >>
> >> >
> >> > On 9 March 2017 at 02:11, Gary Gregory 
> wrote:
> >> >
> >> >> FYI
> >> >> -- Forwarded message --
> >> >> From: 
> >> >> Date: Wed, Mar 8, 2017 at 11:25 PM
> >> >> Subject: New git mirror created: commons-pool.git
> >> >> To: infrastruct...@apache.org, priv...@commons.apache.org
> >> >>
> >> >>
> >> >> New repository commons-pool.git was mirrored to git.a.o (and thus
> >> GitHub),
> >> >> as requested by ggregory.
> >> >> New mirrors are available on GitHub no more than 24 hours later.
> >> >>
> >> >> With regards,
> >> >> Apache Infrastructure.
> >> >>
> >> >> 
> -
> >> >> To unsubscribe, e-mail: private-unsubscr...@commons.apache.org
> >> >> For additional commands, e-mail: private-h...@commons.apache.org
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> >> >> Java Persistence with Hibernate, Second Edition
> >> >>  >> >> tl?ie=UTF8=1789=9325=1617290459&
> >> >> linkCode=as2=garygregory-20=
> cadb800f39946ec62ea2b1af9fe6a2
> >> b8>
> >> >>
> >> >>  garygregory-20=am2=1=
> >> >> 1617290459>
> >> >> JUnit in Action, Second Edition
> >> >>  >> >> tl?ie=UTF8=1789=9325=1935182021&
> >> >> linkCode=as2=garygregory-20=
> 31ecd1f6b6d1eaf8886ac902a24de4
> >> 18%22
> >> >>>
> >> >>
> >> >>  garygregory-20=am2=1=
> >> >> 1935182021>
> >> >> Spring Batch in Action
> >> >>  >> >> tl?ie=UTF8=1789=9325=1935182951&
> >> >> linkCode=%7B%7BlinkCode%7D%7D=garygregory-20=%7B%
> >> >> 7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
> >> >>  garygregory-20=am2=1=
> >> >> 1935182951>
> >> >> Blog: http://garygregory.wordpress.com
> >> >> Home: http://garygregory.com/
> >> >> Tweet! http://twitter.com/GaryGregory
> >> >>
> >> >
> >> >
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
> >
> >
> > --
> > Matt Sicker 
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Matt Sicker

Re: New git mirror created: commons-pool.git

2017-03-09 Thread Matt Sicker 
I made a request the other day to move commons-pool, and they told me it
was all self-serve now and they'd provide help if needed.

On 9 March 2017 at 15:24, Benedikt Ritter  wrote:

> Hi,
>
> > Am 09.03.2017 um 21:30 schrieb Oliver Heger <
> oliver.he...@oliver-heger.de>:
> >
> > Hi,
> >
> > Am 09.03.2017 um 15:58 schrieb Matt Sicker:
> >> Thanks! I don't think I'll be able to convert the repo until tomorrow,
> >> however.
> >
> > I would be interested to also move [configuration] to git, but - as
> > usual - am pretty busy currently. Is there a documentation somewhere for
> > the single steps that need to be done?
>
> We have some documentation in the wiki [1]. However it starts only after
> INFRA has moved the repo. What you have to do is to create an INFRA ticket
> asking them to migrate the component. It is good to tell them, that there
> already is a git mirror and a GitHub mirror so they know that those have to
> be updated as well. After the repo has been migrated, follow the steps in
> the wiki documentation.
>
> Regards,
> Benedikt
>
> [1] https://wiki.apache.org/commons/MovingToGit
>
> >
> > Thanks
> > Oliver
> >
> >>
> >> On 9 March 2017 at 02:11, Gary Gregory  wrote:
> >>
> >>> FYI
> >>> -- Forwarded message --
> >>> From: 
> >>> Date: Wed, Mar 8, 2017 at 11:25 PM
> >>> Subject: New git mirror created: commons-pool.git
> >>> To: infrastruct...@apache.org, priv...@commons.apache.org
> >>>
> >>>
> >>> New repository commons-pool.git was mirrored to git.a.o (and thus
> GitHub),
> >>> as requested by ggregory.
> >>> New mirrors are available on GitHub no more than 24 hours later.
> >>>
> >>> With regards,
> >>> Apache Infrastructure.
> >>>
> >>> -
> >>> To unsubscribe, e-mail: private-unsubscr...@commons.apache.org
> >>> For additional commands, e-mail: private-h...@commons.apache.org
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> >>> Java Persistence with Hibernate, Second Edition
> >>>  >>> tl?ie=UTF8=1789=9325=1617290459&
> >>> linkCode=as2=garygregory-20=cadb800f39946ec62ea2b1af9fe6a2
> b8>
> >>>
> >>>  >>> 1617290459>
> >>> JUnit in Action, Second Edition
> >>>  >>> tl?ie=UTF8=1789=9325=1935182021&
> >>> linkCode=as2=garygregory-20=31ecd1f6b6d1eaf8886ac902a24de4
> 18%22
> 
> >>>
> >>>  >>> 1935182021>
> >>> Spring Batch in Action
> >>>  >>> tl?ie=UTF8=1789=9325=1935182951&
> >>> linkCode=%7B%7BlinkCode%7D%7D=garygregory-20=%7B%
> >>> 7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
> >>>  >>> 1935182951>
> >>> Blog: http://garygregory.wordpress.com
> >>> Home: http://garygregory.com/
> >>> Tweet! http://twitter.com/GaryGregory
> >>>
> >>
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org  dev-unsubscr...@commons.apache.org>
> > For additional commands, e-mail: dev-h...@commons.apache.org  dev-h...@commons.apache.org>
>



-- 
Matt Sicker

Re: New git mirror created: commons-pool.git

2017-03-09 Thread sebb 
On 9 March 2017 at 21:24, Matt Sicker  wrote:
> The steps are pretty straightforward now:
>
> 1. Do a lazy majority vote to make sure nobody has problems with the
> migration.
> 2. Create a new git repo via the reporeq webapp.
> 3. Get the authors.txt file: https://git-wip-us.apache.org/authors.txt

Warn devs not to commit to SVN
Record the current SVN revision details

> 4. Use git-svn to import the subversion repo (there are instructions
> somewhere on how to do this so you don't have to scan the entire svn
> history to find the first revision of that subdirectory).

Double-check that SVN has not been changed since the start of the process
If necessary, redo the conversion

> 5. Push that converted repo to the newly created one.

Rename SVN to https://svn.apache.org/repos/asf/commons/_moved_to_git/
and leave text file behind, e.g. as per

https://svn.apache.org/repos/asf/commons/proper/compress/

Moving the SVN tree could be done earlier, to make it less likely that
devs will accidentally commit.

There will probably be some noise from CI jobs whilst the changes are made...

> It's actually somewhat of a pain in the ass and is probably why infra made
> it self-service. ;)
>
> On 9 March 2017 at 14:30, Oliver Heger  wrote:
>
>> Hi,
>>
>> Am 09.03.2017 um 15:58 schrieb Matt Sicker:
>> > Thanks! I don't think I'll be able to convert the repo until tomorrow,
>> > however.
>>
>> I would be interested to also move [configuration] to git, but - as
>> usual - am pretty busy currently. Is there a documentation somewhere for
>> the single steps that need to be done?
>>
>> Thanks
>> Oliver
>>
>> >
>> > On 9 March 2017 at 02:11, Gary Gregory  wrote:
>> >
>> >> FYI
>> >> -- Forwarded message --
>> >> From: 
>> >> Date: Wed, Mar 8, 2017 at 11:25 PM
>> >> Subject: New git mirror created: commons-pool.git
>> >> To: infrastruct...@apache.org, priv...@commons.apache.org
>> >>
>> >>
>> >> New repository commons-pool.git was mirrored to git.a.o (and thus
>> GitHub),
>> >> as requested by ggregory.
>> >> New mirrors are available on GitHub no more than 24 hours later.
>> >>
>> >> With regards,
>> >> Apache Infrastructure.
>> >>
>> >> -
>> >> To unsubscribe, e-mail: private-unsubscr...@commons.apache.org
>> >> For additional commands, e-mail: private-h...@commons.apache.org
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> >> Java Persistence with Hibernate, Second Edition
>> >> > >> tl?ie=UTF8=1789=9325=1617290459&
>> >> linkCode=as2=garygregory-20=cadb800f39946ec62ea2b1af9fe6a2
>> b8>
>> >>
>> >> > >> 1617290459>
>> >> JUnit in Action, Second Edition
>> >> > >> tl?ie=UTF8=1789=9325=1935182021&
>> >> linkCode=as2=garygregory-20=31ecd1f6b6d1eaf8886ac902a24de4
>> 18%22
>> >>>
>> >>
>> >> > >> 1935182021>
>> >> Spring Batch in Action
>> >> > >> tl?ie=UTF8=1789=9325=1935182951&
>> >> linkCode=%7B%7BlinkCode%7D%7D=garygregory-20=%7B%
>> >> 7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
>> >> > >> 1935182951>
>> >> Blog: http://garygregory.wordpress.com
>> >> Home: http://garygregory.com/
>> >> Tweet! http://twitter.com/GaryGregory
>> >>
>> >
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
>
> --
> Matt Sicker 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: New git mirror created: commons-pool.git

2017-03-09 Thread Matt Sicker 
The steps are pretty straightforward now:

1. Do a lazy majority vote to make sure nobody has problems with the
migration.
2. Create a new git repo via the reporeq webapp.
3. Get the authors.txt file: https://git-wip-us.apache.org/authors.txt
4. Use git-svn to import the subversion repo (there are instructions
somewhere on how to do this so you don't have to scan the entire svn
history to find the first revision of that subdirectory).
5. Push that converted repo to the newly created one.

It's actually somewhat of a pain in the ass and is probably why infra made
it self-service. ;)

On 9 March 2017 at 14:30, Oliver Heger  wrote:

> Hi,
>
> Am 09.03.2017 um 15:58 schrieb Matt Sicker:
> > Thanks! I don't think I'll be able to convert the repo until tomorrow,
> > however.
>
> I would be interested to also move [configuration] to git, but - as
> usual - am pretty busy currently. Is there a documentation somewhere for
> the single steps that need to be done?
>
> Thanks
> Oliver
>
> >
> > On 9 March 2017 at 02:11, Gary Gregory  wrote:
> >
> >> FYI
> >> -- Forwarded message --
> >> From: 
> >> Date: Wed, Mar 8, 2017 at 11:25 PM
> >> Subject: New git mirror created: commons-pool.git
> >> To: infrastruct...@apache.org, priv...@commons.apache.org
> >>
> >>
> >> New repository commons-pool.git was mirrored to git.a.o (and thus
> GitHub),
> >> as requested by ggregory.
> >> New mirrors are available on GitHub no more than 24 hours later.
> >>
> >> With regards,
> >> Apache Infrastructure.
> >>
> >> -
> >> To unsubscribe, e-mail: private-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: private-h...@commons.apache.org
> >>
> >>
> >>
> >>
> >> --
> >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> >> Java Persistence with Hibernate, Second Edition
> >>  >> tl?ie=UTF8=1789=9325=1617290459&
> >> linkCode=as2=garygregory-20=cadb800f39946ec62ea2b1af9fe6a2
> b8>
> >>
> >>  >> 1617290459>
> >> JUnit in Action, Second Edition
> >>  >> tl?ie=UTF8=1789=9325=1935182021&
> >> linkCode=as2=garygregory-20=31ecd1f6b6d1eaf8886ac902a24de4
> 18%22
> >>>
> >>
> >>  >> 1935182021>
> >> Spring Batch in Action
> >>  >> tl?ie=UTF8=1789=9325=1935182951&
> >> linkCode=%7B%7BlinkCode%7D%7D=garygregory-20=%7B%
> >> 7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
> >>  >> 1935182951>
> >> Blog: http://garygregory.wordpress.com
> >> Home: http://garygregory.com/
> >> Tweet! http://twitter.com/GaryGregory
> >>
> >
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Matt Sicker

Re: New git mirror created: commons-pool.git

2017-03-09 Thread Benedikt Ritter 
Hi,

> Am 09.03.2017 um 21:30 schrieb Oliver Heger :
> 
> Hi,
> 
> Am 09.03.2017 um 15:58 schrieb Matt Sicker:
>> Thanks! I don't think I'll be able to convert the repo until tomorrow,
>> however.
> 
> I would be interested to also move [configuration] to git, but - as
> usual - am pretty busy currently. Is there a documentation somewhere for
> the single steps that need to be done?

We have some documentation in the wiki [1]. However it starts only after INFRA 
has moved the repo. What you have to do is to create an INFRA ticket asking 
them to migrate the component. It is good to tell them, that there already is a 
git mirror and a GitHub mirror so they know that those have to be updated as 
well. After the repo has been migrated, follow the steps in the wiki 
documentation.

Regards,
Benedikt

[1] https://wiki.apache.org/commons/MovingToGit

> 
> Thanks
> Oliver
> 
>> 
>> On 9 March 2017 at 02:11, Gary Gregory  wrote:
>> 
>>> FYI
>>> -- Forwarded message --
>>> From: 
>>> Date: Wed, Mar 8, 2017 at 11:25 PM
>>> Subject: New git mirror created: commons-pool.git
>>> To: infrastruct...@apache.org, priv...@commons.apache.org
>>> 
>>> 
>>> New repository commons-pool.git was mirrored to git.a.o (and thus GitHub),
>>> as requested by ggregory.
>>> New mirrors are available on GitHub no more than 24 hours later.
>>> 
>>> With regards,
>>> Apache Infrastructure.
>>> 
>>> -
>>> To unsubscribe, e-mail: private-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: private-h...@commons.apache.org
>>> 
>>> 
>>> 
>>> 
>>> --
>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> >> tl?ie=UTF8=1789=9325=1617290459&
>>> linkCode=as2=garygregory-20=cadb800f39946ec62ea2b1af9fe6a2b8>
>>> 
>>> >> 1617290459>
>>> JUnit in Action, Second Edition
>>> >> tl?ie=UTF8=1789=9325=1935182021&
>>> linkCode=as2=garygregory-20=31ecd1f6b6d1eaf8886ac902a24de418%22
 
>>> 
>>> >> 1935182021>
>>> Spring Batch in Action
>>> >> tl?ie=UTF8=1789=9325=1935182951&
>>> linkCode=%7B%7BlinkCode%7D%7D=garygregory-20=%7B%
>>> 7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
>>> >> 1935182951>
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>> 
>> 
>> 
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org 
> 
> For additional commands, e-mail: dev-h...@commons.apache.org 
>

Re: New git mirror created: commons-pool.git

2017-03-09 Thread Oliver Heger 
Hi,

Am 09.03.2017 um 15:58 schrieb Matt Sicker:
> Thanks! I don't think I'll be able to convert the repo until tomorrow,
> however.

I would be interested to also move [configuration] to git, but - as
usual - am pretty busy currently. Is there a documentation somewhere for
the single steps that need to be done?

Thanks
Oliver

> 
> On 9 March 2017 at 02:11, Gary Gregory  wrote:
> 
>> FYI
>> -- Forwarded message --
>> From: 
>> Date: Wed, Mar 8, 2017 at 11:25 PM
>> Subject: New git mirror created: commons-pool.git
>> To: infrastruct...@apache.org, priv...@commons.apache.org
>>
>>
>> New repository commons-pool.git was mirrored to git.a.o (and thus GitHub),
>> as requested by ggregory.
>> New mirrors are available on GitHub no more than 24 hours later.
>>
>> With regards,
>> Apache Infrastructure.
>>
>> -
>> To unsubscribe, e-mail: private-unsubscr...@commons.apache.org
>> For additional commands, e-mail: private-h...@commons.apache.org
>>
>>
>>
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second Edition
>> > tl?ie=UTF8=1789=9325=1617290459&
>> linkCode=as2=garygregory-20=cadb800f39946ec62ea2b1af9fe6a2b8>
>>
>> > 1617290459>
>> JUnit in Action, Second Edition
>> > tl?ie=UTF8=1789=9325=1935182021&
>> linkCode=as2=garygregory-20=31ecd1f6b6d1eaf8886ac902a24de418%22
>>>
>>
>> > 1935182021>
>> Spring Batch in Action
>> > tl?ie=UTF8=1789=9325=1935182951&
>> linkCode=%7B%7BlinkCode%7D%7D=garygregory-20=%7B%
>> 7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
>> > 1935182951>
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
> 
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Build failed in Jenkins: Commons-configuration #49

2017-03-09 Thread Oliver Heger 


Am 09.03.2017 um 09:36 schrieb Dennis Kieselhorst:
> Changed the build from JDK 1.6 to JDK 1.7 to fix that.
> 
> See also https://issues.apache.org/jira/browse/INFRA-13556

Great! Many thanks!

Oliver

> 
> Regards
> Dennis
> 
> Am 08.03.2017 um 22:03 schrieb Apache Jenkins Server:
>> Parsing POMs
>> Established TCP socket on 44316
>> maven33-agent.jar already up to date
>> maven33-interceptor.jar already up to date
>> maven3-interceptor-commons.jar already up to date
>> [Commons-configuration] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx2g 
>> -Xms256m -cp 
>> /home/jenkins/jenkins-slave/maven33-agent.jar:/home/jenkins/tools/maven/latest3/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/latest3/conf/logging
>>  jenkins.maven3.agent.Maven33Main /home/jenkins/tools/maven/latest3/ 
>> /home/jenkins/jenkins-slave/slave.jar 
>> /home/jenkins/jenkins-slave/maven33-interceptor.jar 
>> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 44316
>> Native maven support requires Java 1.7 or later, but this Maven is using 
>> /usr/local/asfpackages/java/jdk1.6.0_45-64/jre
>> Please use the freestyle project.
>> ERROR: Failed to launch Maven. Exit code = 1
>>
>>
> 
> 
> -
> 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: [ALL][Math] git pull requests: how?

2017-03-09 Thread Gilles 

On Thu, 9 Mar 2017 12:01:08 -0600, Matt Sicker wrote:

Try viewing the log like this:

git log --oneline --decorate --graph

It might be farther back in time,


Oh yes, of course, you are right.
I tested this with a fairly old pull request!

Thanks and sorry for the noise,
Gilles


so the added commits won't show up at the
top of the normal git log format.

On 9 March 2017 at 11:48, Gilles  
wrote:



On Thu, 9 Mar 2017 11:34:42 -0600, Matt Sicker wrote:

A merge commit is an additional commit unless you squash what 
you're
merging. The entire history should be available. You can use --ff 
to only
allow a fast forward commit so it doesn't add a merge commit, but 
then the
branch you're merging has be to rebased on the one you're merging 
into.




I did

$ git pull github pull/50/head

in a local copy of Commons Math "master" branch.

The command performed a single commit (a "merge") and there is no
trace that the change(s) were coming from someone else (a GitHub 
user):


  https://github.com/apache/commons-math/pull/50/commits/b32cd
65abb0497fa35ca407430f20d562f604ed7

$ git log
commit 68fdf0620ecfc708a940cfd02451986cc42fde5b
Merge: 37c3d36c8 b32cd65ab
Author: Gilles 
Date:   Thu Mar 9 16:01:07 2017 +0100

Merge commit 'refs/pull/50/head' of 
https://github.com/apache/comm

ons-math into fix-MATH-1402

[No other commit related to that action.]


Gilles




On 9 March 2017 at 09:08, Gilles  
wrote:


On Thu, 9 Mar 2017 09:38:55 -0500, Rob Tompkins wrote:


On Mar 9, 2017, at 8:08 AM, Gilles  
wrote:




On Wed, 8 Mar 2017 10:37:44 -0600, Matt Sicker wrote:

The "write to a PR branch" was something I mentioned in a 
different

email.

If you want a single command to merge a PR into master, 
assuming

you've
already set up "github" as your github remote:



$ git remote -v
githubhttps://github.com/apache/commons-math.git (fetch)
githubhttps://github.com/apache/commons-math.git (push)
origin
https://git-wip-us.apache.org/repos/asf/commons-math.git

(fetch)
origin
https://git-wip-us.apache.org/repos/asf/commons-math.git

(push)


git pull github pull/42

git push

Something like that should work.



$ git pull github pull/50
fatal: Couldn't find remote ref pull/50

Am I missing something?


Try


git pull github pull/#/head



It successfully performs a merge into the current branch, but does
not preserve the commit history (only the merge appears in "git 
log").


IIRC, the generated instructions[1] would lead to the 
contributor's

commit being referenced properly.

Regards,
Gilles

[1] Such as in:
  https://issues.apache.org/jira/browse/NUMBERS-4




-Rob


Regards,


Gilles

[...]










-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [ALL][Math] git pull requests: how?

2017-03-09 Thread Matt Sicker 
Try viewing the log like this:

git log --oneline --decorate --graph

It might be farther back in time, so the added commits won't show up at the
top of the normal git log format.

On 9 March 2017 at 11:48, Gilles  wrote:

> On Thu, 9 Mar 2017 11:34:42 -0600, Matt Sicker wrote:
>
>> A merge commit is an additional commit unless you squash what you're
>> merging. The entire history should be available. You can use --ff to only
>> allow a fast forward commit so it doesn't add a merge commit, but then the
>> branch you're merging has be to rebased on the one you're merging into.
>>
>
> I did
>
> $ git pull github pull/50/head
>
> in a local copy of Commons Math "master" branch.
>
> The command performed a single commit (a "merge") and there is no
> trace that the change(s) were coming from someone else (a GitHub user):
>
>   https://github.com/apache/commons-math/pull/50/commits/b32cd
> 65abb0497fa35ca407430f20d562f604ed7
>
> $ git log
> commit 68fdf0620ecfc708a940cfd02451986cc42fde5b
> Merge: 37c3d36c8 b32cd65ab
> Author: Gilles 
> Date:   Thu Mar 9 16:01:07 2017 +0100
>
> Merge commit 'refs/pull/50/head' of https://github.com/apache/comm
> ons-math into fix-MATH-1402
>
> [No other commit related to that action.]
>
>
> Gilles
>
>
>
>
>> On 9 March 2017 at 09:08, Gilles  wrote:
>>
>> On Thu, 9 Mar 2017 09:38:55 -0500, Rob Tompkins wrote:
>>>
>>> On Mar 9, 2017, at 8:08 AM, Gilles  wrote:

>
> On Wed, 8 Mar 2017 10:37:44 -0600, Matt Sicker wrote:
>
>> The "write to a PR branch" was something I mentioned in a different
>> email.
>>
>> If you want a single command to merge a PR into master, assuming
>> you've
>> already set up "github" as your github remote:
>>
>>
> $ git remote -v
> githubhttps://github.com/apache/commons-math.git (fetch)
> githubhttps://github.com/apache/commons-math.git (push)
> originhttps://git-wip-us.apache.org/repos/asf/commons-math.git
> (fetch)
> originhttps://git-wip-us.apache.org/repos/asf/commons-math.git
> (push)
>
>
> git pull github pull/42
>> git push
>>
>> Something like that should work.
>>
>>
> $ git pull github pull/50
> fatal: Couldn't find remote ref pull/50
>
> Am I missing something?
>
>
> Try

 git pull github pull/#/head


>>> It successfully performs a merge into the current branch, but does
>>> not preserve the commit history (only the merge appears in "git log").
>>>
>>> IIRC, the generated instructions[1] would lead to the contributor's
>>> commit being referenced properly.
>>>
>>> Regards,
>>> Gilles
>>>
>>> [1] Such as in:
>>>   https://issues.apache.org/jira/browse/NUMBERS-4
>>>
>>>
>>>
>>>
>>> -Rob

 Regards,

> Gilles
>
> [...]
>
>>
>>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Matt Sicker

Re: [ALL][Math] git pull requests: how?

2017-03-09 Thread Gilles 

On Thu, 9 Mar 2017 11:34:42 -0600, Matt Sicker wrote:

A merge commit is an additional commit unless you squash what you're
merging. The entire history should be available. You can use --ff to 
only
allow a fast forward commit so it doesn't add a merge commit, but 
then the
branch you're merging has be to rebased on the one you're merging 
into.


I did

$ git pull github pull/50/head

in a local copy of Commons Math "master" branch.

The command performed a single commit (a "merge") and there is no
trace that the change(s) were coming from someone else (a GitHub user):

  
https://github.com/apache/commons-math/pull/50/commits/b32cd65abb0497fa35ca407430f20d562f604ed7


$ git log
commit 68fdf0620ecfc708a940cfd02451986cc42fde5b
Merge: 37c3d36c8 b32cd65ab
Author: Gilles 
Date:   Thu Mar 9 16:01:07 2017 +0100

Merge commit 'refs/pull/50/head' of 
https://github.com/apache/commons-math into fix-MATH-1402


[No other commit related to that action.]


Gilles




On 9 March 2017 at 09:08, Gilles  
wrote:



On Thu, 9 Mar 2017 09:38:55 -0500, Rob Tompkins wrote:

On Mar 9, 2017, at 8:08 AM, Gilles  
wrote:


On Wed, 8 Mar 2017 10:37:44 -0600, Matt Sicker wrote:
The "write to a PR branch" was something I mentioned in a 
different

email.

If you want a single command to merge a PR into master, assuming 
you've

already set up "github" as your github remote:



$ git remote -v
githubhttps://github.com/apache/commons-math.git (fetch)
githubhttps://github.com/apache/commons-math.git (push)
originhttps://git-wip-us.apache.org/repos/asf/commons-math.git
(fetch)
originhttps://git-wip-us.apache.org/repos/asf/commons-math.git
(push)



git pull github pull/42
git push

Something like that should work.



$ git pull github pull/50
fatal: Couldn't find remote ref pull/50

Am I missing something?



Try

git pull github pull/#/head



It successfully performs a merge into the current branch, but does
not preserve the commit history (only the merge appears in "git 
log").


IIRC, the generated instructions[1] would lead to the contributor's
commit being referenced properly.

Regards,
Gilles

[1] Such as in:
  https://issues.apache.org/jira/browse/NUMBERS-4





-Rob

Regards,

Gilles

[...]








-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [ALL][Math] git pull requests: how?

2017-03-09 Thread Matt Sicker 
A merge commit is an additional commit unless you squash what you're
merging. The entire history should be available. You can use --ff to only
allow a fast forward commit so it doesn't add a merge commit, but then the
branch you're merging has be to rebased on the one you're merging into.

On 9 March 2017 at 09:08, Gilles  wrote:

> On Thu, 9 Mar 2017 09:38:55 -0500, Rob Tompkins wrote:
>
>> On Mar 9, 2017, at 8:08 AM, Gilles  wrote:
>>>
>>> On Wed, 8 Mar 2017 10:37:44 -0600, Matt Sicker wrote:
 The "write to a PR branch" was something I mentioned in a different
 email.

 If you want a single command to merge a PR into master, assuming you've
 already set up "github" as your github remote:

>>>
>>> $ git remote -v
>>> githubhttps://github.com/apache/commons-math.git (fetch)
>>> githubhttps://github.com/apache/commons-math.git (push)
>>> originhttps://git-wip-us.apache.org/repos/asf/commons-math.git
>>> (fetch)
>>> originhttps://git-wip-us.apache.org/repos/asf/commons-math.git
>>> (push)
>>>
>>>
 git pull github pull/42
 git push

 Something like that should work.

>>>
>>> $ git pull github pull/50
>>> fatal: Couldn't find remote ref pull/50
>>>
>>> Am I missing something?
>>>
>>>
>> Try
>>
>> git pull github pull/#/head
>>
>
> It successfully performs a merge into the current branch, but does
> not preserve the commit history (only the merge appears in "git log").
>
> IIRC, the generated instructions[1] would lead to the contributor's
> commit being referenced properly.
>
> Regards,
> Gilles
>
> [1] Such as in:
>   https://issues.apache.org/jira/browse/NUMBERS-4
>
>
>
>
>> -Rob
>>
>> Regards,
>>> Gilles
>>>
>>> [...]

>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Matt Sicker

Re: [ALL][Math] git pull requests: how?

2017-03-09 Thread Gilles 

On Thu, 9 Mar 2017 09:38:55 -0500, Rob Tompkins wrote:
On Mar 9, 2017, at 8:08 AM, Gilles  
wrote:



On Wed, 8 Mar 2017 10:37:44 -0600, Matt Sicker wrote:
The "write to a PR branch" was something I mentioned in a different 
email.


If you want a single command to merge a PR into master, assuming 
you've

already set up "github" as your github remote:


$ git remote -v
githubhttps://github.com/apache/commons-math.git (fetch)
githubhttps://github.com/apache/commons-math.git (push)
originhttps://git-wip-us.apache.org/repos/asf/commons-math.git 
(fetch)
originhttps://git-wip-us.apache.org/repos/asf/commons-math.git 
(push)




git pull github pull/42
git push

Something like that should work.


$ git pull github pull/50
fatal: Couldn't find remote ref pull/50

Am I missing something?



Try

git pull github pull/#/head


It successfully performs a merge into the current branch, but does
not preserve the commit history (only the merge appears in "git log").

IIRC, the generated instructions[1] would lead to the contributor's
commit being referenced properly.

Regards,
Gilles

[1] Such as in:
  https://issues.apache.org/jira/browse/NUMBERS-4




-Rob


Regards,
Gilles


[...]





-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: New git mirror created: commons-pool.git

2017-03-09 Thread Matt Sicker 
Thanks! I don't think I'll be able to convert the repo until tomorrow,
however.

On 9 March 2017 at 02:11, Gary Gregory  wrote:

> FYI
> -- Forwarded message --
> From: 
> Date: Wed, Mar 8, 2017 at 11:25 PM
> Subject: New git mirror created: commons-pool.git
> To: infrastruct...@apache.org, priv...@commons.apache.org
>
>
> New repository commons-pool.git was mirrored to git.a.o (and thus GitHub),
> as requested by ggregory.
> New mirrors are available on GitHub no more than 24 hours later.
>
> With regards,
> Apache Infrastructure.
>
> -
> To unsubscribe, e-mail: private-unsubscr...@commons.apache.org
> For additional commands, e-mail: private-h...@commons.apache.org
>
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
>  tl?ie=UTF8=1789=9325=1617290459&
> linkCode=as2=garygregory-20=cadb800f39946ec62ea2b1af9fe6a2b8>
>
>  1617290459>
> JUnit in Action, Second Edition
>  tl?ie=UTF8=1789=9325=1935182021&
> linkCode=as2=garygregory-20=31ecd1f6b6d1eaf8886ac902a24de418%22
> >
>
>  1935182021>
> Spring Batch in Action
>  tl?ie=UTF8=1789=9325=1935182951&
> linkCode=%7B%7BlinkCode%7D%7D=garygregory-20=%7B%
> 7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
>  1935182951>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Matt Sicker

Re: [ALL][Math] git pull requests: how?

2017-03-09 Thread Rob Tompkins 


> On Mar 9, 2017, at 8:08 AM, Gilles  wrote:
> 
>> On Wed, 8 Mar 2017 10:37:44 -0600, Matt Sicker wrote:
>> The "write to a PR branch" was something I mentioned in a different email.
>> 
>> If you want a single command to merge a PR into master, assuming you've
>> already set up "github" as your github remote:
> 
> $ git remote -v
> githubhttps://github.com/apache/commons-math.git (fetch)
> githubhttps://github.com/apache/commons-math.git (push)
> originhttps://git-wip-us.apache.org/repos/asf/commons-math.git (fetch)
> originhttps://git-wip-us.apache.org/repos/asf/commons-math.git (push)
> 
>> 
>> git pull github pull/42
>> git push
>> 
>> Something like that should work.
> 
> $ git pull github pull/50
> fatal: Couldn't find remote ref pull/50
> 
> Am I missing something?
> 

Try

git pull github pull/#/head

-Rob

> Regards,
> Gilles
> 
>> [...]
> 
> 
> -
> 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

[VOTE] Release Apache Commons CLI 1.4 based on RC1

2017-03-09 Thread Benedikt Ritter 
Hi,

We have fixed some bugs and added two new features since CLI 1.3.1 was released,
so I would like to release CLI 1.4.

CLI 1.4 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/ (svn 
revision 18640)

The tag is here:
http://svn.apache.org/repos/asf/commons/proper/cli/tags/cli-1.4-RC1/ (svn 
revision 1786159)
N.B. the SVN revision is required because SVN tags are not immutable.

Maven artifacts are here:
  https://repository.apache.org/content/repositories/orgapachecommons-1240

These are the Maven Artifacts and their hashes:

commons-cli-1.4.pom.asc
(SHA1: 94f01d5c45d00d7cfda8f7d0b8e16f57318b02a3)
commons-cli-1.4-test-sources.jar
(SHA1: 98e1c62e29f0c86c0bd8361cf6fdb59c8a106ff4)
commons-cli-1.4.jar
(SHA1: c51c00206bb913cd8612b24abd9fa98ae89719b1)
commons-cli-1.4-sources.jar.asc
(SHA1: 80a7676aba577faafd8278e9b321abaa426f3b45)
commons-cli-1.4-tests.jar
(SHA1: 1e39d7027793ce92342b10abb4d6437826211534)
commons-cli-1.4-tests.jar.asc
(SHA1: a558a4e58802af24ce58404df98b8c5737297bc9)
commons-cli-1.4-javadoc.jar.asc
(SHA1: d67ed3fea7b0346fcfa2a3c9c4092741ce6a84a7)
commons-cli-1.4-sources.jar
(SHA1: 40dfd9fdef125e19136135e68d54af6d9b0cfbb8)
commons-cli-1.4-javadoc.jar
(SHA1: 60090d1d137b0dd7a0c293d04fb2280a7eec3860)
commons-cli-1.4-test-sources.jar.asc
(SHA1: 180e61b1fba50d93291e4cbf35bbdfc0ba04a43f)
commons-cli-1.4.jar.asc
(SHA1: d6a040cbdc4789aeabe74f8e9f9602c7bd430541)
commons-cli-1.4.pom
(SHA1: c5aed4264ff37247043f6dcb6613d994ea7f8473)

I have tested this with JDK 1.7 and JDK 1.8 using Maven 3.3.9. Note that CLI 
required at least Java 5 and I haven’t tested this release with 1.5 or 1.6. If 
anybody has such old JDKs installed, I would appreciate some feedback on this.

Details of changes since 1.3.1 are in the release notes:
  
https://dist.apache.org/repos/dist/dev/commons/cli/cli-1.4-RC1/RELEASE-NOTES.txt
  http://home.apache.org/~britter/commons/cli/1.4-RC1/changes-report.html

Site:
  http://home.apache.org/~britter/commons/cli/1.4-RC1/
  (note some *relative* links are broken and the 1.4 directories are not yet 
created - these will be OK once the site is deployed)

Clirr Report (compared to 1.3.1):
  http://home.apache.org/~britter/commons/cli/1.4-RC1/clirr-report.html
(Sorry, after updating to commons-parent 42 the clirr report was not generated 
anymore. I had to do it by hand, that’s why it has a different style)

RAT Report:
  http://home.apache.org/~britter/commons/cli/1.4-RC1/rat-report.html

KEYS:
  https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner that 72 hours from now,
i.e. sometime after 13:30 UTC 12-March 2017

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

Thanks!

Benedikt




-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [ALL][Math] git pull requests: how?

2017-03-09 Thread Gilles 

On Wed, 8 Mar 2017 10:37:44 -0600, Matt Sicker wrote:
The "write to a PR branch" was something I mentioned in a different 
email.


If you want a single command to merge a PR into master, assuming 
you've

already set up "github" as your github remote:


$ git remote -v
github  https://github.com/apache/commons-math.git (fetch)
github  https://github.com/apache/commons-math.git (push)
origin  https://git-wip-us.apache.org/repos/asf/commons-math.git (fetch)
origin  https://git-wip-us.apache.org/repos/asf/commons-math.git (push)



git pull github pull/42
git push

Something like that should work.


$ git pull github pull/50
fatal: Couldn't find remote ref pull/50

Am I missing something?

Regards,
Gilles


[...]



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [JENKINS] fixing builds that require less than Java 7

2017-03-09 Thread Benedikt Ritter 
Hi,

> Am 09.03.2017 um 13:29 schrieb sebb :
> 
> Jenkins now requires Java 7 for running Maven builds
> 
> However it is possible to use the -Pjava-1.6 (etc) profiles to
> continue to build with the target JVM
> 
> 1) Update the main JVM to at least 1.7 so Jenkins-Maven works
> 
> 2) add -Pjava-1.n to the Maven command line
> 
> 3) Add the definition of JAVA_1_N_HOME to the job:
> 
> Build Environment
> Inject environment variables to the build process
> Properties Content: JAVA_1_N_HOME=/home/jenkins/tools/java/latest1.N/
> 
> The path in the above line is taken from:
> 
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
> 
> This is the approach used in Commons Validator, Net, Pool (and now CLI)

Thank you for fixing this for CLI (which I’m currently working on).

> 
> As an alternative, the JAVA_1_N_HOME variable can be defined in terms
> of one of the 'Tool Environment' variables. e.g.
> 
> JAVA_1_5_HOME=${JDK_1_5_LATEST__HOME}
> 
> This avoids having to use the actual path name.
> 
> Unfortunately there don't seem to be any Java settings that apply to
> all nodes; the Windows paths and names are different from the Ubuntu
> ones.
> 
> -
> 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

[JENKINS] fixing builds that require less than Java 7

2017-03-09 Thread sebb 
Jenkins now requires Java 7 for running Maven builds

However it is possible to use the -Pjava-1.6 (etc) profiles to
continue to build with the target JVM

1) Update the main JVM to at least 1.7 so Jenkins-Maven works

2) add -Pjava-1.n to the Maven command line

3) Add the definition of JAVA_1_N_HOME to the job:

Build Environment
Inject environment variables to the build process
Properties Content: JAVA_1_N_HOME=/home/jenkins/tools/java/latest1.N/

The path in the above line is taken from:

https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix

This is the approach used in Commons Validator, Net, Pool (and now CLI)

As an alternative, the JAVA_1_N_HOME variable can be defined in terms
of one of the 'Tool Environment' variables. e.g.

JAVA_1_5_HOME=${JDK_1_5_LATEST__HOME}

This avoids having to use the actual path name.

Unfortunately there don't seem to be any Java settings that apply to
all nodes; the Windows paths and names are different from the Ubuntu
ones.

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Jenkins build is back to normal : commons-cli #17

2017-03-09 Thread Apache Jenkins Server 
See 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Build failed in Jenkins: commons-cli #16

2017-03-09 Thread Apache Jenkins Server 
See 

Changes:

[britter] Make CheckStyle happy

[britter] Exclude .htaccess file from RAT report

[britter] Add description for next release

[britter] Add CLI-269 to changes.xml

--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on beam4 (beam) in workspace 

Checking out a fresh workspace because there's no workspace at 

Cleaning local Directory .
Checking out https://svn.apache.org/repos/asf/commons/proper/cli/trunk at 
revision '2017-03-09T11:48:42.776 +'
AUNOTICE.txt
AULICENSE.txt
AURELEASE-NOTES.txt
A .travis.yml
A CONTRIBUTING.md
A src
A src/changes
AUsrc/changes/changes.xml
A src/assembly
AUsrc/assembly/src.xml
AUsrc/assembly/bin.xml
A src/media
AUsrc/media/logo.xcf
A src/test
A src/test/java
A src/test/java/org
A src/test/java/org/apache
A src/test/java/org/apache/commons
A src/test/java/org/apache/commons/cli
AUsrc/test/java/org/apache/commons/cli/CommandLineTest.java
AUsrc/test/java/org/apache/commons/cli/ParserTestCase.java
AUsrc/test/java/org/apache/commons/cli/OptionsTest.java
A src/test/java/org/apache/commons/cli/bug
AUsrc/test/java/org/apache/commons/cli/bug/BugCLI13Test.java
AUsrc/test/java/org/apache/commons/cli/bug/BugCLI133Test.java
AUsrc/test/java/org/apache/commons/cli/bug/BugCLI71Test.java
AUsrc/test/java/org/apache/commons/cli/bug/BugCLI162Test.java
AUsrc/test/java/org/apache/commons/cli/bug/BugCLI18Test.java
A src/test/java/org/apache/commons/cli/bug/BugCLI252Test.java
AUsrc/test/java/org/apache/commons/cli/bug/BugsTest.java
AUsrc/test/java/org/apache/commons/cli/bug/BugCLI148Test.java
AUsrc/test/java/org/apache/commons/cli/bug/BugCLI265Test.java
A src/test/java/org/apache/commons/cli/bug/BugCLI266Test.java
AUsrc/test/java/org/apache/commons/cli/BasicParserTest.java
AUsrc/test/java/org/apache/commons/cli/ValuesTest.java
AUsrc/test/java/org/apache/commons/cli/DefaultParserTest.java
AUsrc/test/java/org/apache/commons/cli/ApplicationTest.java
AUsrc/test/java/org/apache/commons/cli/GnuParserTest.java
AUsrc/test/java/org/apache/commons/cli/ArgumentIsOptionTest.java
AUsrc/test/java/org/apache/commons/cli/OptionTest.java
AUsrc/test/java/org/apache/commons/cli/HelpFormatterTest.java
AUsrc/test/java/org/apache/commons/cli/ValueTest.java
AUsrc/test/java/org/apache/commons/cli/PatternOptionBuilderTest.java
AUsrc/test/java/org/apache/commons/cli/UtilTest.java
AUsrc/test/java/org/apache/commons/cli/OptionBuilderTest.java
AUsrc/test/java/org/apache/commons/cli/PosixParserTest.java
AUsrc/test/java/org/apache/commons/cli/OptionGroupTest.java
A src/test/resources
A src/main
A src/main/java
A src/main/java/org
A src/main/java/org/apache
A src/main/java/org/apache/commons
A src/main/java/org/apache/commons/cli
AUsrc/main/java/org/apache/commons/cli/UnrecognizedOptionException.java
AUsrc/main/java/org/apache/commons/cli/GnuParser.java
AUsrc/main/java/org/apache/commons/cli/Option.java
AUsrc/main/java/org/apache/commons/cli/AlreadySelectedException.java
AUsrc/main/java/org/apache/commons/cli/HelpFormatter.java
AUsrc/main/java/org/apache/commons/cli/Util.java
AUsrc/main/java/org/apache/commons/cli/PatternOptionBuilder.java
AUsrc/main/java/org/apache/commons/cli/OptionValidator.java
AUsrc/main/java/org/apache/commons/cli/TypeHandler.java
AUsrc/main/java/org/apache/commons/cli/PosixParser.java
AUsrc/main/java/org/apache/commons/cli/OptionBuilder.java
AUsrc/main/java/org/apache/commons/cli/MissingOptionException.java
AUsrc/main/java/org/apache/commons/cli/package-info.java
AUsrc/main/java/org/apache/commons/cli/OptionGroup.java
AUsrc/main/java/org/apache/commons/cli/CommandLine.java
AUsrc/main/java/org/apache/commons/cli/ParseException.java
AUsrc/main/java/org/apache/commons/cli/overview.html
AUsrc/main/java/org/apache/commons/cli/Options.java
AUsrc/main/java/org/apache/commons/cli/MissingArgumentException.java
AUsrc/main/java/org/apache/commons/cli/Parser.java
AUsrc/main/java/org/apache/commons/cli/BasicParser.java
AUsrc/main/java/org/apache/commons/cli/DefaultParser.java
AUsrc/main/java/org/apache/commons/cli/AmbiguousOptionException.java
AUsrc/main/java/org/apache/commons/cli/CommandLineParser.java
A src/site
A

Fwd: New git mirror created: commons-pool.git

2017-03-09 Thread Gary Gregory 
FYI
-- Forwarded message --
From: 
Date: Wed, Mar 8, 2017 at 11:25 PM
Subject: New git mirror created: commons-pool.git
To: infrastruct...@apache.org, priv...@commons.apache.org


New repository commons-pool.git was mirrored to git.a.o (and thus GitHub),
as requested by ggregory.
New mirrors are available on GitHub no more than 24 hours later.

With regards,
Apache Infrastructure.

-
To unsubscribe, e-mail: private-unsubscr...@commons.apache.org
For additional commands, e-mail: private-h...@commons.apache.org




-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition



JUnit in Action, Second Edition



Spring Batch in Action


Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Jenkins build is back to normal : Commons-configuration #51

2017-03-09 Thread Apache Jenkins Server 
See 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Build failed in Jenkins: Commons-configuration #49

2017-03-09 Thread Dennis Kieselhorst 
Changed the build from JDK 1.6 to JDK 1.7 to fix that.

See also https://issues.apache.org/jira/browse/INFRA-13556

Regards
Dennis

Am 08.03.2017 um 22:03 schrieb Apache Jenkins Server:
> Parsing POMs
> Established TCP socket on 44316
> maven33-agent.jar already up to date
> maven33-interceptor.jar already up to date
> maven3-interceptor-commons.jar already up to date
> [Commons-configuration] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx2g 
> -Xms256m -cp 
> /home/jenkins/jenkins-slave/maven33-agent.jar:/home/jenkins/tools/maven/latest3/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/latest3/conf/logging
>  jenkins.maven3.agent.Maven33Main /home/jenkins/tools/maven/latest3/ 
> /home/jenkins/jenkins-slave/slave.jar 
> /home/jenkins/jenkins-slave/maven33-interceptor.jar 
> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 44316
> Native maven support requires Java 1.7 or later, but this Maven is using 
> /usr/local/asfpackages/java/jdk1.6.0_45-64/jre
> Please use the freestyle project.
> ERROR: Failed to launch Maven. Exit code = 1
>
>


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Build failed in Jenkins: Commons-configuration #50

2017-03-09 Thread Apache Jenkins Server 
See 

--
Started by user Dennis Kieselhorst
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-us1 (ubuntu) in workspace 

Updating http://svn.apache.org/repos/asf/commons/proper/configuration/trunk at 
revision '2017-03-09T08:26:01.742 +'
U 
src/main/java/org/apache/commons/configuration2/ConfigurationUtils.java
U 
src/main/java/org/apache/commons/configuration2/ConfigurationConverter.java
U pom.xml
At revision 1786108

No changes for 
http://svn.apache.org/repos/asf/commons/proper/configuration/trunk since the 
previous build
Parsing POMs
Established TCP socket on 54843
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[Commons-configuration] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx2g 
-Xms256m -cp 
/home/jenkins/jenkins-slave/maven32-agent.jar:/home/jenkins/tools/maven/apache-maven-3.2.5/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/apache-maven-3.2.5/conf/logging
 jenkins.maven3.agent.Maven32Main /home/jenkins/tools/maven/apache-maven-3.2.5 
/home/jenkins/jenkins-slave/slave.jar 
/home/jenkins/jenkins-slave/maven32-interceptor.jar 
/home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 54843
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
hudson/remoting/Launcher : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:401)
at 
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:254)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:143)
at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:74)
ERROR: Failed to parse POMs
java.io.EOFException: unexpected stream termination
at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:365)
at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:310)
at hudson.slaves.Channels.forProcess(Channels.java:115)
at 
hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:294)
at hudson.maven.ProcessCache.get(ProcessCache.java:236)
at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:798)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1728)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:544)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Fwd: New git repository created: commons-pool.git

2017-03-09 Thread Gary Gregory 
FYI.

-- Forwarded message --
From: 
Date: Wed, Mar 8, 2017 at 11:20 PM
Subject: New git repository created: commons-pool.git
To: infrastruct...@apache.org, priv...@commons.apache.org


New repository commons-pool.git was created, as requested by ggregory.
You may view it at: https://git-wip-us.apache.org/repos/asf/commons-pool.git

With regards,
Apache Infrastructure.

-
To unsubscribe, e-mail: private-unsubscr...@commons.apache.org
For additional commands, e-mail: private-h...@commons.apache.org




-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition



JUnit in Action, Second Edition



Spring Batch in Action


Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [VOTE][RESULT] Migrate commons-pool to git

2017-03-09 Thread Gary Gregory 
Done:

https://git-wip-us.apache.org/repos/asf?p=commons-pool.git

Gary

On Wed, Mar 8, 2017 at 10:39 PM, Gary Gregory 
wrote:

> Done. It may take up to an hour for the request to be completed.
>
> Gary
>
> On Wed, Mar 8, 2017 at 6:06 PM, Matt Sicker  wrote:
>
>> Looks like I need a PMC to create a repository via here:
>> https://reporeq.apache.org/
>>
>> Then I can run svn2git locally apparently and just sync it up myself.
>>
>> On 8 March 2017 at 19:19, Matt Sicker  wrote:
>>
>> > https://issues.apache.org/jira/browse/INFRA-13630
>> >
>> > On 8 March 2017 at 19:13, Matt Sicker  wrote:
>> >
>> >> The vote passes by lazy approval with two +1 votes from Gary Gregory
>> and
>> >> myself and no -1 votes.
>> >>
>> >> I'll make an infra ticket to get us migrated. Please don't commit
>> >> anything to commons-pool for a little while so that nothing gets out of
>> >> sync during the migration.
>> >>
>> >> --
>> >> Matt Sicker 
>> >>
>> >
>> >
>> >
>> > --
>> > Matt Sicker 
>> >
>>
>>
>>
>> --
>> Matt Sicker 
>>
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
>
> 
> JUnit in Action, Second Edition
> 
>
> 
> Spring Batch in Action
> 
> 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition



JUnit in Action, Second Edition



Spring Batch in Action


Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory