Build failed in Jenkins: commons-jexl #20

2017-03-10 Thread Apache Jenkins Server 
See 


Changes:

[henrib] JEXL:
Various updates & improvements related to last fixes

[henrib] JEXL-211:
Add callable method to JexlExpression interface - breaks compatibility but it 
is not expected than any codeimplements this interface besides Jexl

[henrib] JEXL-216:
Use r/w lock on cache, busy-flag logic on parser (parser is not reentrant, 
create a temp one if busy)

[henrib] JEXL-211:
Protect various executors from null properties in tryInvoke

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

Updating https://svn.apache.org/repos/asf/commons/proper/jexl/trunk at revision 
'2017-03-10T15:09:13.595 +'
U RELEASE-NOTES.txt
U src/main/java/org/apache/commons/jexl3/JexlExpression.java
U src/main/java/org/apache/commons/jexl3/internal/Script.java
U src/main/java/org/apache/commons/jexl3/internal/Engine.java
U 
src/main/java/org/apache/commons/jexl3/internal/introspection/DuckSetExecutor.java
U 
src/main/java/org/apache/commons/jexl3/internal/introspection/IndexedType.java
U 
src/main/java/org/apache/commons/jexl3/internal/introspection/MapGetExecutor.java
U 
src/main/java/org/apache/commons/jexl3/internal/introspection/BooleanGetExecutor.java
U 
src/main/java/org/apache/commons/jexl3/internal/introspection/DuckGetExecutor.java
U 
src/main/java/org/apache/commons/jexl3/internal/introspection/MapSetExecutor.java
U src/main/java/org/apache/commons/jexl3/internal/InterpreterBase.java
AUsrc/main/java/org/apache/commons/jexl3/internal/SoftCache.java
U src/main/java/org/apache/commons/jexl3/internal/TemplateEngine.java
U src/site/xdoc/changes.xml
U src/test/java/org/apache/commons/jexl3/internal/Util.java
U src/test/java/org/apache/commons/jexl3/AnnotationTest.java
U src/test/java/org/apache/commons/jexl3/IssuesTest.java
U src/test/java/org/apache/commons/jexl3/JexlEvalContext.java
U pom.xml
At revision 1786362

Parsing POMs
Modules changed, recalculating dependency graph
Established TCP socket on 38134
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[commons-jexl] $ /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 38134
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

Re: [jexl] 3.1 release review

2017-03-10 Thread henrib 
Resurrecting the thread...Hopefully Emmanuel has a few spare cycles. :-)
I've commented JEXL-220 with the 3 Clirr errors that correspond to adding
methods to interfaces that only Jexl is supposed to implement. 
I've also added a very clear statements as a waning in the release-notes; it
reads as:
{code}

Warning:

This release does break compatibility by adding methods to interfaces; these
interfaces are not expected to be
implemented by code external to the Jexl project and this compatibility
break should remain hypothetical.
It is however possible and we are sorry if it causes problems to any of you.
To mitigate this issue, besides continue using JEXL 3.0, you are likely
delegating to JEXL3 objects and you
shall be able to continue doing so with these new methods. The 3 interfaces
& methods are:

1 - 'public java.lang.Boolean isCancellable()' in interface
org.apache.commons.jexl3.JexlEngine$Options
2 - 'public java.util.concurrent.Callable
callable(org.apache.commons.jexl3.JexlContext)'in interface
org.apache.commons.jexl3.JexlExpression
3 - 'public java.util.Map getPragmas()'in interface
org.apache.commons.jexl3.JxltEngine$Template

{code}

Is this acceptable ?



--
View this message in context: 
http://apache-commons.680414.n4.nabble.com/jexl-3-1-release-review-tp4691513p4696356.html
Sent from the Commons - Dev mailing list archive at Nabble.com.

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

[GitHub] commons-rdf pull request #33: COMMONSRDF-59 - fix minor javadocs warnings

2017-03-10 Thread acoburn 
GitHub user acoburn opened a pull request:

https://github.com/apache/commons-rdf/pull/33

COMMONSRDF-59 - fix minor javadocs warnings

This add some missing `@return` values, fixes an HTML error and adds some 
text to two otherwise undocumented parameters.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/acoburn/commons-rdf COMMONSRDF-59

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/commons-rdf/pull/33.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #33


commit 18b5ecfc56cf1e37e752761bcaa694096fdcea04
Author: Aaron Coburn 
Date:   2017-03-10T17:05:26Z

COMMONSRDF-59 - fix minor javadocs warnings




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Build failed in Jenkins: commons-jexl #21

2017-03-10 Thread Apache Jenkins Server 
See 


Changes:

[henrib] JEXL:
Removed (wrong) statement about Java7

[henrib] JEXL:
Added clear statement about compatibility break

[henrib] JEXL:
Avoiding clirr error

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

Updating https://svn.apache.org/repos/asf/commons/proper/jexl/trunk at revision 
'2017-03-10T17:09:08.486 +'
U RELEASE-NOTES.txt
U src/main/java/org/apache/commons/jexl3/introspection/JexlSandbox.java
At revision 1786390

Parsing POMs
Established TCP socket on 35073
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[commons-jexl] $ /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 35073
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

[GitHub] commons-rdf pull request #34: COMMONSRDF-60: update commons-parent version

2017-03-10 Thread acoburn 
GitHub user acoburn opened a pull request:

https://github.com/apache/commons-rdf/pull/34

COMMONSRDF-60: update commons-parent version

This upgrades the parent pom to the latest version of `commons-parent`.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/acoburn/commons-rdf COMMONSRDF-60

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/commons-rdf/pull/34.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #34


commit 5b03234a13560706575d6ddb9db493811d5181f2
Author: Aaron Coburn 
Date:   2017-03-10T17:14:57Z

COMMONSRDF-60: update commons-parent version




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
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-jexl #22

2017-03-10 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: [VOTE] Release Commons Text 1.0 based on RC1

2017-03-10 Thread Rob Tompkins 
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
>  
> 
> 
> 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-10 Thread Bruno P. Kinoshita 
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
> 
>
> 
> 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-10 Thread Matt Sicker 
If you change the artefacts, that's a new release candidate. New vote, too.

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