date:20170311

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

2017-03-11 Thread Gary Gregory

On Sat, Mar 11, 2017 at 10:02 AM, Matt Sicker  wrote:

> Welp, I'm stuck on step one.
>
> $ svn mkdir -m"POOL => Git"
> https://svn.apache.org/repos/asf/commons/_moved_to_git/pool
> svn: E175013: Access to
> '/repos/asf/!svn/txr/1786516-137xq/commons/_moved_to_git/pool' forbidden
>

Done.

Committing transaction...
Committed revision 1786557.

Gary


> On 9 March 2017 at 17:02, Matt Sicker  wrote:
>
> > 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&camp=1789&creative=9325&creativeASIN=1617290459&
> >> >> >> linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b
> >> 1af9fe6a2
> >> >> b8>
> >> >> >>
> >> >> >>  >> am2&o=1&a=
> >> >> >> 1617290459>
> >> >> >> JUnit in Action, Second Edition
> >> >> >>  >> >> >> tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&
> >> >> >> linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac
> >> 902a24de4
> >> >> 18%22
> >> >> >>>
> >> >> >>
> >> >> >>  >> am2&o=1&a=
> >> >> >> 1935182021>
> >> >> >> Spring Batch in Action
> >> >> >>  >> >> >> tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&
> >> >> >> linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%
> >> >> >> 7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
> >> >> >>  >> am2&o=1&a=
> >> >> >> 1935182951>
> >> >> >> Blog: http://garygregory.wordpress.com
> >> >> >> Home: http://garygregory.com/
> >> >> >> Tweet! http://twitter.com/GaryGregory
> >> >> >>
> >> >> >
> >> >> >
> >> >> >

Re: [text] Please add your release data for 'commons'

2017-03-11 Thread Rob Tompkins

Thanks a ton.

-Rob

> On Mar 11, 2017, at 8:36 PM, Bruno P. Kinoshita 
>  wrote:
> 
> Added 1.0, release date to 11/Mar/2017, since that's the current day in your 
> time and also UTC (it's the 12th for me)
> 
> TEXT-1.0: 2017-03-11
> 
> Cheers and kudos for the release!
> Bruno
> 
> 
> - Original Message -
> From: Rob Tompkins 
> To: Commons Developers List 
> Sent: Sunday, 12 March 2017 2:25 PM
> Subject: [text] Please add your release data for 'commons'
> 
> I don’t have the karma to perform this action. I was wondering if someone (in 
> the PMC) could hop in and lend a hand with this release task.
> 
> Many thanks,
> -Rob
> 
>> On Mar 11, 2017, at 8:22 PM, Apache Reporter Service 
>>  wrote:
>> 
>> Hi,
>> This is an automated email from reporter.apache.org.
>> I see that you just pushed something to our release repository for the 
>> 'commons' project
>> in the following commit:
>> 
>> r18687 at 2017-03-12 01:12:58 + (Sun, 12 Mar 2017)
>> Release Commons Text 1.0 based on RC1
>> See also: r18688
>> 
>> If you are a PMC member of this project, we ask that you log on to:
>> https://reporter.apache.org/addrelease.html?commons
>> and add your release data (version and date) to the database.
>> 
>> If you are not a PMC member, please have a PMC member add this information.
>> 
>> While this is not a requirement, we ask that you still add this data to the
>> reporter database, so that people using the Apache Reporter Service will be
>> able to see the latest release data for this project.
>> 
>> Also, please ensure that you remove [1] any older releases.
>> 
>> With regards,
>> The Apache Reporter Service.
>> 
>> [1] http://www.apache.org/dev/release.html#when-to-archive
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


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

Re: [text] Please add your release data for 'commons'

2017-03-11 Thread Bruno P. Kinoshita

Added 1.0, release date to 11/Mar/2017, since that's the current day in your 
time and also UTC (it's the 12th for me)

TEXT-1.0: 2017-03-11

Cheers and kudos for the release!
Bruno


- Original Message -
From: Rob Tompkins 
To: Commons Developers List 
Sent: Sunday, 12 March 2017 2:25 PM
Subject: [text] Please add your release data for 'commons'

I don’t have the karma to perform this action. I was wondering if someone (in 
the PMC) could hop in and lend a hand with this release task.

Many thanks,
-Rob

> On Mar 11, 2017, at 8:22 PM, Apache Reporter Service 
>  wrote:
> 
> Hi,
> This is an automated email from reporter.apache.org.
> I see that you just pushed something to our release repository for the 
> 'commons' project
> in the following commit:
> 
> r18687 at 2017-03-12 01:12:58 + (Sun, 12 Mar 2017)
> Release Commons Text 1.0 based on RC1
> See also: r18688
> 
> If you are a PMC member of this project, we ask that you log on to:
> https://reporter.apache.org/addrelease.html?commons
> and add your release data (version and date) to the database.
> 
> If you are not a PMC member, please have a PMC member add this information.
> 
> While this is not a requirement, we ask that you still add this data to the
> reporter database, so that people using the Apache Reporter Service will be
> able to see the latest release data for this project.
> 
> Also, please ensure that you remove [1] any older releases.
> 
> With regards,
> The Apache Reporter Service.
> 
> [1] http://www.apache.org/dev/release.html#when-to-archive
> 


-
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

[text] Please add your release data for 'commons'

2017-03-11 Thread Rob Tompkins

I don’t have the karma to perform this action. I was wondering if someone (in 
the PMC) could hop in and lend a hand with this release task.

Many thanks,
-Rob

> On Mar 11, 2017, at 8:22 PM, Apache Reporter Service 
>  wrote:
> 
> Hi,
> This is an automated email from reporter.apache.org.
> I see that you just pushed something to our release repository for the 
> 'commons' project
> in the following commit:
> 
> r18687 at 2017-03-12 01:12:58 + (Sun, 12 Mar 2017)
> Release Commons Text 1.0 based on RC1
> See also: r18688
> 
> If you are a PMC member of this project, we ask that you log on to:
> https://reporter.apache.org/addrelease.html?commons
> and add your release data (version and date) to the database.
> 
> If you are not a PMC member, please have a PMC member add this information.
> 
> While this is not a requirement, we ask that you still add this data to the
> reporter database, so that people using the Apache Reporter Service will be
> able to see the latest release data for this project.
> 
> Also, please ensure that you remove [1] any older releases.
> 
> With regards,
> The Apache Reporter Service.
> 
> [1] http://www.apache.org/dev/release.html#when-to-archive
> 


-
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-11 Thread Oliver Heger

Hi,

build works fine with Java 1.5 and 1.8 on Windows 10, artifacts and site
look good.

I noticed the following minor things:
- 54 unit tests are skipped which is a high number given the total
number of 372. It may be worth having a look at those and remove
outdated or fix broken ones.
- The Javadoc (opened from both the link below "User Guide" and the
reports section) shows version Commons CLI 1.3 (direct on the index
page); not sure why here an older version appears.

This is not blocking, so +1.

Oliver

Am 09.03.2017 um 14:30 schrieb 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
> 

-
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-11 Thread Benedikt Ritter

This can only be done by members of the PMC. I'm on my mobile right know.
Can anybody else please jump in?

Benedikt

Matt Sicker  schrieb am Sa. 11. März 2017 um 19:07:

> Welp, I'm stuck on step one.
>
> $ svn mkdir -m"POOL => Git"
> https://svn.apache.org/repos/asf/commons/_moved_to_git/pool
> svn: E175013: Access to
> '/repos/asf/!svn/txr/1786516-137xq/commons/_moved_to_git/pool' forbidden
>
> On 9 March 2017 at 17:02, Matt Sicker  wrote:
>
> > 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&camp=1789&creative=9325&creativeASIN=1617290459&
> >> >> >> linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b
> >> 1af9fe6a2
> >> >> b8>
> >> >> >>
> >> >> >>  >> am2&o=1&a=
> >> >> >> 1617290459>
> >> >> >> JUnit in Action, Second Edition
> >> >> >>  >> >> >> tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&
> >> >> >> linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac
> >> 902a24de4
> >> >> 18%22
> >> >> >>>
> >> >> >>
> >> >> >>  >> am2&o=1&a=
> >> >> >> 1935182021>
> >> >> >> Spring Batch in Action
> >> >> >>  >> >> >> tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&
> >> >> >> linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%
> >> >> >> 7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
> >> >> >>  >> am2&o=1&a=
> >> >> >> 1935182951>
> >> >> >> Blog: http://garygregory.wordpress.com
> >> >> >> Home: http://garygregory.com/
> >> >> >> Tweet! http://twitter.com/GaryGre

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

2017-03-11 Thread Matt Sicker

Welp, I'm stuck on step one.

$ svn mkdir -m"POOL => Git"
https://svn.apache.org/repos/asf/commons/_moved_to_git/pool
svn: E175013: Access to
'/repos/asf/!svn/txr/1786516-137xq/commons/_moved_to_git/pool' forbidden

On 9 March 2017 at 17:02, Matt Sicker  wrote:

> 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&camp=1789&creative=9325&creativeASIN=1617290459&
>> >> >> linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b
>> 1af9fe6a2
>> >> b8>
>> >> >>
>> >> >> > am2&o=1&a=
>> >> >> 1617290459>
>> >> >> JUnit in Action, Second Edition
>> >> >> > >> >> tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&
>> >> >> linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac
>> 902a24de4
>> >> 18%22
>> >> >>>
>> >> >>
>> >> >> > am2&o=1&a=
>> >> >> 1935182021>
>> >> >> Spring Batch in Action
>> >> >> > >> >> tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&
>> >> >> linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%
>> >> >> 7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
>> >> >> > am2&o=1&a=
>> >> >> 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.

[RESULT][VOTE] Release Commons Text 1.0 based on RC1

2017-03-11 Thread Rob Tompkins

The vote passes with the following (in order of appearance):

Bruno P. Kinoshita: +1
Oliver Heger: +1
Jörg Schaible: +1, and
Rob Tompkins: +1 (non-binding)

I will proceed with publishing the release candidate. Many thanks to all of 
those that helped in preparing and validating this release.

Cheers,
-Rob

> On Mar 6, 2017, at 8:25 AM, Rob Tompkins  wrote:
> 
> Hello all,
> 
> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
> 
> Tag name:
>commons-text-1.0-RC1 (signature can be checked from git using 'git tag
> -v')
> 
> Tag URL:
>
> https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e
>  
> 
> 
> Commit ID the tag points at:
>e38039a3da2244741f5d33ab1b05bdee51c53c3e
> 
> Site:
>http://home.apache.org/~chtompki/commons-text-1.0-RC1 
> 
> 
> Distribution files (committed at revision 18567):
>https://dist.apache.org/repos/dist/dev/commons/text/ 
> 
> 
> Distribution files hashes (SHA1):
>commons-text-1.0-bin.tar.gz
>(SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>commons-text-1.0-bin.zip
>(SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>commons-text-1.0-src.tar.gz
>(SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>commons-text-1.0-src.zip
>(SHA1: d838bb107bcdbe58bba0525f8fd7341a2b40)
> 
> These are the Maven artifacts and their hashes:
>commons-text-1.0-javadoc.jar
>(SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>commons-text-1.0-sources.jar
>(SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>commons-text-1.0-test-sources.jar
>(SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>commons-text-1.0-tests.jar
>(SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>commons-text-1.0.jar
>(SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>commons-text-1.0.pom
>(SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
> 
> KEYS file to check signatures:
>http://www.apache.org/dist/commons/KEYS 
> 
> 
> Maven artifacts:
>https://repository.apache.org/content/repositories/orgapachecommons-1239 
> 
> 
> Please select one of the following options[1]:
>   [ ] +1 Release it.
>   [ ] +0 Go ahead; I don't care.
>   [ ] -0 There are a few minor glitches: ...
>   [ ] -1 No, do not release it because ...
> 
> This vote will be open at least 72 hours, i.e. until 
> 2017-03-09T14:00:00Z
> (this is UTC time).
> 
> 
> Cheers,
> -Rob
> 
> [1] http://apache.org/foundation/voting.html 
>

Re: [VOTE] Release Commons Text 1.0 based on RC1

2017-03-11 Thread Rob Tompkins

Here’s my +1 (non-binding).

> On Mar 6, 2017, at 8:25 AM, Rob Tompkins  wrote:
> 
> Hello all,
> 
> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
> 
> Tag name:
>commons-text-1.0-RC1 (signature can be checked from git using 'git tag
> -v')
> 
> Tag URL:
>
> https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e
>  
> 
> 
> Commit ID the tag points at:
>e38039a3da2244741f5d33ab1b05bdee51c53c3e
> 
> Site:
>http://home.apache.org/~chtompki/commons-text-1.0-RC1 
> 
> 
> Distribution files (committed at revision 18567):
>https://dist.apache.org/repos/dist/dev/commons/text/ 
> 
> 
> Distribution files hashes (SHA1):
>commons-text-1.0-bin.tar.gz
>(SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>commons-text-1.0-bin.zip
>(SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>commons-text-1.0-src.tar.gz
>(SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>commons-text-1.0-src.zip
>(SHA1: d838bb107bcdbe58bba0525f8fd7341a2b40)
> 
> These are the Maven artifacts and their hashes:
>commons-text-1.0-javadoc.jar
>(SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>commons-text-1.0-sources.jar
>(SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>commons-text-1.0-test-sources.jar
>(SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>commons-text-1.0-tests.jar
>(SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>commons-text-1.0.jar
>(SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>commons-text-1.0.pom
>(SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
> 
> KEYS file to check signatures:
>http://www.apache.org/dist/commons/KEYS 
> 
> 
> Maven artifacts:
>https://repository.apache.org/content/repositories/orgapachecommons-1239 
> 
> 
> Please select one of the following options[1]:
>   [ ] +1 Release it.
>   [ ] +0 Go ahead; I don't care.
>   [ ] -0 There are a few minor glitches: ...
>   [ ] -1 No, do not release it because ...
> 
> This vote will be open at least 72 hours, i.e. until 
> 2017-03-09T14:00:00Z
> (this is UTC time).
> 
> 
> Cheers,
> -Rob
> 
> [1] http://apache.org/foundation/voting.html 
>

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

2017-03-11 Thread Robert Scholte


+1 and thanks for picking this up, really appreciate it.

thanks,
Robert

On Thu, 09 Mar 2017 14:30:28 +0100, 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 Commons Text 1.0 based on RC1

2017-03-11 Thread Rob Tompkins



> On Mar 11, 2017, at 10:11 AM, sebb  wrote:
> 
>> On 11 March 2017 at 14:41, Rob Tompkins  wrote:
>> 
>>> On Mar 10, 2017, at 10:38 PM, Matt Sicker  wrote:
>>> 
>>> If you change the artefacts, that's a new release candidate. New vote, too.
>> 
>> Yes, definitely, I would need to create a new tag and go through the entire 
>> build process again. I’m just offering to do that so that the 1.0 release is 
>> cleaner. That said, we do have three +1’s so I’m definitely on the fence 
>> about making that call.
> 
> If the RN text error is the only problem would say it would be better
> to release as is.
> 
> Just make sure that the docmentation that accompanies the release
> clarifies the issue.
> e.g. the Announce mail and website.
> 
> The copy of the RN which is uploaded to the ASF mirror servers could
> also be fixed.
> Probably best to add a prologue to say that the text was fixed after
> release so people
> are not confused if they notice that it disagrees with the RN in the
> source/binary bundles.

Okay, I'll send out the result and do the release over the next day or so. 

Cheers,
-Rob

> 
>> -Rob
>> 
>>> 
>>> On 10 March 2017 at 20:23, Bruno P. Kinoshita <
>>> brunodepau...@yahoo.com.br.invalid> wrote:
>>> 
 I have never been a RM, but maybe generate new artefacts with the
 corrected text files, then release it and send the notes to the announce
 e-mail?
 Users can trace the reason for the changes in your commit message and here
 in the vote thread.
 CheersBruno
 From: Rob Tompkins 
 To: dev@commons.apache.org
 Sent: Saturday, 11 March 2017 2:12 PM
 Subject: Re: [VOTE] Release Commons Text 1.0 based on RC1
 
 The vote can pass with the following (in order of appearance):
 
 Bruno P. Kinoshita: +1
 Oliver Heger: +1
 Jörg Schaible: +1.
 
 Personally, I’m in the +/- 0 area for the reasons that Oliver and Sebb
 stated.
 
 I’m entirely willing to re-build the candidate to get a “spotless” 1.0
 release. Does anyone have any thoughts regarding the value of having fewer
 typographical errors in a 1.0 release?
 
 If we do go out with it, what would the process be: make sure to make the
 notes in the [ANNOUNCE] email?
 
 -Rob
 
> On Mar 6, 2017, at 8:25 AM, Rob Tompkins  wrote:
> 
> Hello all,
> 
> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
> 
> Tag name:
>  commons-text-1.0-RC1 (signature can be checked from git using 'git tag
> -v')
> 
> Tag URL:
>  https://git-wip-us.apache.org/repos/asf?p=commons-text.git;
 a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e <
 https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
 e38039a3da2244741f5d33ab1b05bdee51c53c3e>
> 
> Commit ID the tag points at:
>  e38039a3da2244741f5d33ab1b05bdee51c53c3e
> 
> Site:
>  http://home.apache.org/~chtompki/commons-text-1.0-RC1 <
 http://home.apache.org/~chtompki/commons-text-1.0-RC1>
> 
> Distribution files (committed at revision 18567):
>  https://dist.apache.org/repos/dist/dev/commons/text/ <
 https://dist.apache.org/repos/dist/dev/commons/text/>
> 
> Distribution files hashes (SHA1):
>  commons-text-1.0-bin.tar.gz
>  (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>  commons-text-1.0-bin.zip
>  (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>  commons-text-1.0-src.tar.gz
>  (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>  commons-text-1.0-src.zip
>  (SHA1: d838bb107bcdbe58bba0525f8fd7341a2b40)
> 
> These are the Maven artifacts and their hashes:
>  commons-text-1.0-javadoc.jar
>  (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>  commons-text-1.0-sources.jar
>  (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>  commons-text-1.0-test-sources.jar
>  (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>  commons-text-1.0-tests.jar
>  (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>  commons-text-1.0.jar
>  (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>  commons-text-1.0.pom
>  (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
> 
> KEYS file to check signatures:
>  http://www.apache.org/dist/commons/KEYS 
> 
> Maven artifacts:
>  https://repository.apache.org/content/repositories/
 orgapachecommons-1239 
> 
> Please select one of the following options[1]:
> [ ] +1 Release it.
> [ ] +0 Go ahead; I don't care.
> [ ] -0 There are a few minor glitches: ...
> [ ] -1 No, do not release it because ...
> 
> This vote will be open at least 72 hours, i.e. until
> 2017-03-09T14:00:00Z
> (this is UTC time).
> 
> 
> Cheers,
> -Rob
> 
> [1] http://apache.org

Re: [VOTE] Release Commons Text 1.0 based on RC1

2017-03-11 Thread sebb

On 11 March 2017 at 14:41, Rob Tompkins  wrote:
>
>> On Mar 10, 2017, at 10:38 PM, Matt Sicker  wrote:
>>
>> If you change the artefacts, that's a new release candidate. New vote, too.
>
> Yes, definitely, I would need to create a new tag and go through the entire 
> build process again. I’m just offering to do that so that the 1.0 release is 
> cleaner. That said, we do have three +1’s so I’m definitely on the fence 
> about making that call.

If the RN text error is the only problem would say it would be better
to release as is.

Just make sure that the docmentation that accompanies the release
clarifies the issue.
e.g. the Announce mail and website.

The copy of the RN which is uploaded to the ASF mirror servers could
also be fixed.
Probably best to add a prologue to say that the text was fixed after
release so people
are not confused if they notice that it disagrees with the RN in the
source/binary bundles.

> -Rob
>
>>
>> On 10 March 2017 at 20:23, Bruno P. Kinoshita <
>> brunodepau...@yahoo.com.br.invalid> wrote:
>>
>>> I have never been a RM, but maybe generate new artefacts with the
>>> corrected text files, then release it and send the notes to the announce
>>> e-mail?
>>> Users can trace the reason for the changes in your commit message and here
>>> in the vote thread.
>>> CheersBruno
>>>  From: Rob Tompkins 
>>> To: dev@commons.apache.org
>>> Sent: Saturday, 11 March 2017 2:12 PM
>>> Subject: Re: [VOTE] Release Commons Text 1.0 based on RC1
>>>
>>> The vote can pass with the following (in order of appearance):
>>>
>>> Bruno P. Kinoshita: +1
>>> Oliver Heger: +1
>>> Jörg Schaible: +1.
>>>
>>> Personally, I’m in the +/- 0 area for the reasons that Oliver and Sebb
>>> stated.
>>>
>>> I’m entirely willing to re-build the candidate to get a “spotless” 1.0
>>> release. Does anyone have any thoughts regarding the value of having fewer
>>> typographical errors in a 1.0 release?
>>>
>>> If we do go out with it, what would the process be: make sure to make the
>>> notes in the [ANNOUNCE] email?
>>>
>>> -Rob
>>>
 On Mar 6, 2017, at 8:25 AM, Rob Tompkins  wrote:

 Hello all,

 This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).

 Tag name:
   commons-text-1.0-RC1 (signature can be checked from git using 'git tag
 -v')

 Tag URL:
   https://git-wip-us.apache.org/repos/asf?p=commons-text.git;
>>> a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e <
>>> https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
>>> e38039a3da2244741f5d33ab1b05bdee51c53c3e>

 Commit ID the tag points at:
   e38039a3da2244741f5d33ab1b05bdee51c53c3e

 Site:
   http://home.apache.org/~chtompki/commons-text-1.0-RC1 <
>>> http://home.apache.org/~chtompki/commons-text-1.0-RC1>

 Distribution files (committed at revision 18567):
   https://dist.apache.org/repos/dist/dev/commons/text/ <
>>> https://dist.apache.org/repos/dist/dev/commons/text/>

 Distribution files hashes (SHA1):
   commons-text-1.0-bin.tar.gz
   (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
   commons-text-1.0-bin.zip
   (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
   commons-text-1.0-src.tar.gz
   (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
   commons-text-1.0-src.zip
   (SHA1: d838bb107bcdbe58bba0525f8fd7341a2b40)

 These are the Maven artifacts and their hashes:
   commons-text-1.0-javadoc.jar
   (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
   commons-text-1.0-sources.jar
   (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
   commons-text-1.0-test-sources.jar
   (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
   commons-text-1.0-tests.jar
   (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
   commons-text-1.0.jar
   (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
   commons-text-1.0.pom
   (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)

 KEYS file to check signatures:
   http://www.apache.org/dist/commons/KEYS >> commons/KEYS>

 Maven artifacts:
   https://repository.apache.org/content/repositories/
>>> orgapachecommons-1239 >> orgapachecommons-1239>

 Please select one of the following options[1]:
 [ ] +1 Release it.
 [ ] +0 Go ahead; I don't care.
 [ ] -0 There are a few minor glitches: ...
 [ ] -1 No, do not release it because ...

 This vote will be open at least 72 hours, i.e. until
 2017-03-09T14:00:00Z
 (this is UTC time).
 

 Cheers,
 -Rob

 [1] http://apache.org/foundation/voting.html <
>>> http://apache.org/foundation/voting.html>
>>>
>>>
>>>
>>
>>
>>
>> --
>> Matt Sicker 
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h..

Re: [VOTE] Release Commons Text 1.0 based on RC1

2017-03-11 Thread Rob Tompkins


> On Mar 10, 2017, at 10:38 PM, Matt Sicker  wrote:
> 
> If you change the artefacts, that's a new release candidate. New vote, too.

Yes, definitely, I would need to create a new tag and go through the entire 
build process again. I’m just offering to do that so that the 1.0 release is 
cleaner. That said, we do have three +1’s so I’m definitely on the fence about 
making that call.

-Rob

> 
> On 10 March 2017 at 20:23, Bruno P. Kinoshita <
> brunodepau...@yahoo.com.br.invalid> wrote:
> 
>> I have never been a RM, but maybe generate new artefacts with the
>> corrected text files, then release it and send the notes to the announce
>> e-mail?
>> Users can trace the reason for the changes in your commit message and here
>> in the vote thread.
>> CheersBruno
>>  From: Rob Tompkins 
>> To: dev@commons.apache.org
>> Sent: Saturday, 11 March 2017 2:12 PM
>> Subject: Re: [VOTE] Release Commons Text 1.0 based on RC1
>> 
>> The vote can pass with the following (in order of appearance):
>> 
>> Bruno P. Kinoshita: +1
>> Oliver Heger: +1
>> Jörg Schaible: +1.
>> 
>> Personally, I’m in the +/- 0 area for the reasons that Oliver and Sebb
>> stated.
>> 
>> I’m entirely willing to re-build the candidate to get a “spotless” 1.0
>> release. Does anyone have any thoughts regarding the value of having fewer
>> typographical errors in a 1.0 release?
>> 
>> If we do go out with it, what would the process be: make sure to make the
>> notes in the [ANNOUNCE] email?
>> 
>> -Rob
>> 
>>> On Mar 6, 2017, at 8:25 AM, Rob Tompkins  wrote:
>>> 
>>> Hello all,
>>> 
>>> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>>> 
>>> Tag name:
>>>   commons-text-1.0-RC1 (signature can be checked from git using 'git tag
>>> -v')
>>> 
>>> Tag URL:
>>>   https://git-wip-us.apache.org/repos/asf?p=commons-text.git;
>> a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e <
>> https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
>> e38039a3da2244741f5d33ab1b05bdee51c53c3e>
>>> 
>>> Commit ID the tag points at:
>>>   e38039a3da2244741f5d33ab1b05bdee51c53c3e
>>> 
>>> Site:
>>>   http://home.apache.org/~chtompki/commons-text-1.0-RC1 <
>> http://home.apache.org/~chtompki/commons-text-1.0-RC1>
>>> 
>>> Distribution files (committed at revision 18567):
>>>   https://dist.apache.org/repos/dist/dev/commons/text/ <
>> https://dist.apache.org/repos/dist/dev/commons/text/>
>>> 
>>> Distribution files hashes (SHA1):
>>>   commons-text-1.0-bin.tar.gz
>>>   (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>>>   commons-text-1.0-bin.zip
>>>   (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>>>   commons-text-1.0-src.tar.gz
>>>   (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>>>   commons-text-1.0-src.zip
>>>   (SHA1: d838bb107bcdbe58bba0525f8fd7341a2b40)
>>> 
>>> These are the Maven artifacts and their hashes:
>>>   commons-text-1.0-javadoc.jar
>>>   (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>>>   commons-text-1.0-sources.jar
>>>   (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>>>   commons-text-1.0-test-sources.jar
>>>   (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>>>   commons-text-1.0-tests.jar
>>>   (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>>>   commons-text-1.0.jar
>>>   (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>>>   commons-text-1.0.pom
>>>   (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>>> 
>>> KEYS file to check signatures:
>>>   http://www.apache.org/dist/commons/KEYS > commons/KEYS>
>>> 
>>> Maven artifacts:
>>>   https://repository.apache.org/content/repositories/
>> orgapachecommons-1239 > orgapachecommons-1239>
>>> 
>>> Please select one of the following options[1]:
>>> [ ] +1 Release it.
>>> [ ] +0 Go ahead; I don't care.
>>> [ ] -0 There are a few minor glitches: ...
>>> [ ] -1 No, do not release it because ...
>>> 
>>> This vote will be open at least 72 hours, i.e. until
>>> 2017-03-09T14:00:00Z
>>> (this is UTC time).
>>> 
>>> 
>>> Cheers,
>>> -Rob
>>> 
>>> [1] http://apache.org/foundation/voting.html <
>> http://apache.org/foundation/voting.html>
>> 
>> 
>> 
> 
> 
> 
> -- 
> Matt Sicker 


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

Re: [lang] Question with the StringEscapeUtils.(un)escapeEcmaScript

2017-03-11 Thread Yasser Zamani



On 3/8/2017 12:21 PM, Benedikt Ritter wrote:
> Hello Yasser,
>
> Sorry for the late reply! I have been on vacation and needed some time to go 
> through all the mails that have piled up :-)
Hello Benedikt , thank you very much for your answer
>
> StringEscapeUtils contains general String escaping routines. It does not 
> focus on business related escaping (how would you draw that line anyway?). 
> escapeEcmaScript just escapes the characters in a String using EcmaScript 
> String rules.
> Can you please provide a failing test case showing the problem you see?
>
Yes, you're right. I mis-used the method. it is for escaping an ecma 
string that can be used inside an another ecma string but I wrongly used 
that  for escape from script injection!
> So „<" and „>“ are not escaped by escapeEcmaScript..
My failure :(
>>
>> And finally just for a curious, why `ESCAPE_ECMASCRIPT` does not include
>> `OctalUnescaper` but `UNESCAPE_ECMASCRIPT = UNESCAPE_JAVA` does?
>
> Again it is because it just escapes according to EcmaScript escaping rules.
It's some weird , you mean escaping ecma script does not need escaping 
octal, but un-escaping ecma script does need also un-escaping octal? 
i.e. inverse of escaping is not equal to unescaping and vice versa.

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

Re: [lang] Question with the StringEscapeUtils.(un)escapeEcmaScript

2017-03-11 Thread Yasser Zamani



On 3/8/2017 12:21 PM, Benedikt Ritter wrote:
> Hello Yasser,
>
> Sorry for the late reply! I have been on vacation and needed some time to go 
> through all the mails that have piled up :-)
Hello Benedikt , thank you very much for your answer
>
> StringEscapeUtils contains general String escaping routines. It does not 
> focus on business related escaping (how would you draw that line anyway?). 
> escapeEcmaScript just escapes the characters in a String using EcmaScript 
> String rules.
> Can you please provide a failing test case showing the problem you see?
>
Yes, you're right. I mis-used the method. it is for escaping an ecma 
string that can be used inside an another ecma string but I wrongly used 
that  for escape from script injection!
> So „<" and „>“ are not escaped by escapeEcmaScript..
My failure :(
>>
>> And finally just for a curious, why `ESCAPE_ECMASCRIPT` does not include
>> `OctalUnescaper` but `UNESCAPE_ECMASCRIPT = UNESCAPE_JAVA` does?
>
> Again it is because it just escapes according to EcmaScript escaping rules.
It's some weird , you mean escaping ecma script does not need escaping 
octal, but un-escaping ecma script does need also un-escaping octal? 
i.e. inverse of escaping is not equal to unescaping and vice versa.

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

Re: [VOTE] Release Commons Text 1.0 based on RC1

2017-03-11 Thread Rob Tompkins

I’ll add my +1 (non-binding) here.

> On Mar 8, 2017, at 1:15 PM, Jörg Schaible  wrote:
> 
> +1
> 
> Builds fine with my compiler zoo incl. Java 9.
> 
> Rob Tompkins wrote:
> 
>> Hello all,
>> 
>> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>> 
>> Tag name:
>>   commons-text-1.0-RC1 (signature can be checked from git using 'git tag
>> -v')
>> 
>> Tag URL:
>>   https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
>> e38039a3da2244741f5d33ab1b05bdee51c53c3e
>> 
>> Commit ID the tag points at:
>>   e38039a3da2244741f5d33ab1b05bdee51c53c3e
>> 
>> Site:
>>   http://home.apache.org/~chtompki/commons-text-1.0-RC1
>> 
>> Distribution files (committed at revision 18567):
>>   https://dist.apache.org/repos/dist/dev/commons/text/
>> 
>> Distribution files hashes (SHA1):
>>   commons-text-1.0-bin.tar.gz
>>   (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>>   commons-text-1.0-bin.zip
>>   (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>>   commons-text-1.0-src.tar.gz
>>   (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>>   commons-text-1.0-src.zip
>>   (SHA1: d838bb107bcdbe58bba0525f8fd7341a2b40)
>> 
>> These are the Maven artifacts and their hashes:
>>   commons-text-1.0-javadoc.jar
>>   (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>>   commons-text-1.0-sources.jar
>>   (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>>   commons-text-1.0-test-sources.jar
>>   (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>>   commons-text-1.0-tests.jar
>>   (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>>   commons-text-1.0.jar
>>   (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>>   commons-text-1.0.pom
>>   (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>> 
>> KEYS file to check signatures:
>>   http://www.apache.org/dist/commons/KEYS
>> 
>> Maven artifacts:
>> 
> https://repository.apache.org/content/repositories/orgapachecommons-1239
>> 
>> Please select one of the following options[1]:
>>  [ ] +1 Release it.
>>  [ ] +0 Go ahead; I don't care.
>>  [ ] -0 There are a few minor glitches: ...
>>  [ ] -1 No, do not release it because ...
>> 
>> This vote will be open at least 72 hours, i.e. until
>> 2017-03-09T14:00:00Z
>> (this is UTC time).
>> 
>> 
>> Cheers,
>> -Rob
>> 
>> [1] http://apache.org/foundation/voting.html
> 
> 
> 
> -
> 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

Re: [text] Please add your release data for 'commons'

Re: [text] Please add your release data for 'commons'

[text] Please add your release data for 'commons'

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

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

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

[RESULT][VOTE] Release Commons Text 1.0 based on RC1

Re: [VOTE] Release Commons Text 1.0 based on RC1

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

Re: [VOTE] Release Commons Text 1.0 based on RC1

Re: [VOTE] Release Commons Text 1.0 based on RC1

Re: [VOTE] Release Commons Text 1.0 based on RC1

Re: [lang] Question with the StringEscapeUtils.(un)escapeEcmaScript

Re: [lang] Question with the StringEscapeUtils.(un)escapeEcmaScript

Re: [VOTE] Release Commons Text 1.0 based on RC1

16 matches

Site Navigation

Mail list logo

Footer information