[VOTE] Release Commons Collections 4.1 Based on RC1

2015-11-22 Thread Thomas Neidhart 
Hi all,

we have accumulated enough changes since the last 4.0 release as well as
we need to provide a fix for the known remote code exploit via java
de-serialization. Therefore, I would like to start a vote to release
Commons Collections 4.1 based on RC1.

Note:

The fix for the security related issue results in Clirr errors as unsafe
classes in the functor package do not implement the Serializable
interface anymore. This is mentioned in the release notes.


Collections 4.1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/collections/
(svn revision 11263)

Maven artifacts are here:


https://repository.apache.org/content/repositories/orgapachecommons-1122/org/apache/commons/commons-collections4/4.1/

Details of changes since 4.0 are in the release notes:


https://dist.apache.org/repos/dist/dev/commons/collections/RELEASE-NOTES.txt


http://people.apache.org/builds/commons/collections/4.1/RC1/changes-report.html

The tag is here:


https://svn.apache.org/repos/asf/commons/proper/collections/tags/COLLECTIONS_4_1_RC1
(svn revision 1715703)

Site:
http://people.apache.org/builds/commons/collections/4.1/RC1/

Clirr Report (compared to 4.0):


http://people.apache.org/builds/commons/collections/4.1/RC1/clirr-report.html

RAT Report:


http://people.apache.org/builds/commons/collections/4.1/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. after 2400
GMT 25-November 2015

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

Thanks,

Thomas

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

Re: [VOTE] Release Validator 1.5.0 based on RC1

2015-11-22 Thread Thomas Neidhart 
On 11/19/2015 10:48 AM, sebb wrote:
> It's probably about time to release VALIDATOR.
> There have been quite a few improvements and fixes since the last version.
> 
> ==
> 
> Validator 1.5.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/validator/ (svn
> revision 11236)
> 
> ./binaries/commons-validator-1.5.0-bin.tar.gz.sha1:d1ec43eee78475675787db4ce478f03e9089a38f
> ./binaries/commons-validator-1.5.0-bin.zip.sha1:de3664516fdf68667d10b8d060eebd0cf1e349c5
> ./source/commons-validator-1.5.0-src.tar.gz.sha1:737f4df692f3d64bd8c0c6ba6c39e1a7533309c0
> ./source/commons-validator-1.5.0-src.zip.sha1:690c353b52359e75a6b5f0bd1b0cf0f34067c544
> 
>   Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1118/commons-validator/commons-validator/1.5.0/
> 
> These are the artifacts and their hashes
> 
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-tests.jar
> (SHA1: 371f755d033b4a5d4a8b799e453e27e8211179a7)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0.pom
> (SHA1: 4050c881a79cd5e621339c749ef03b47eb851a4a)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0.jar
> (SHA1: 26b98c21975c5caf6bf34bacdeb7183be7a65970)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-javadoc.jar
> (SHA1: f3f3364cb4b3e9d9b0362b2bb2770a579ec76a64)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-sources.jar
> (SHA1: 96c77b61d4ed9ca3b58a7a40bac7fa98a09f5c2f)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-test-sources.jar
> (SHA1: 68e7c52affe4fdc98d4431e6b9ffcc30969279a1)
> 
>   Details of changes since 1.4.1 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/validator/RELEASE-NOTES.txt
> http://people.apache.org/~sebb/validator-1.5.0-RC1/changes-report.html
> 
>   I have tested this with JDK 1.6, 1.7, 1.8 using maven3.
> 
>   The tag is here:
> 
> http://svn.apache.org/repos/asf/commons/proper/validator/tags/VALIDATOR_1_5_0_RC1/
> (svn 1715135)
>   N.B. the SVN revision is required because SVN tags are not immutable.
> 
>   Site:
> http://people.apache.org/~sebb/validator-1.5.0-RC1/
>   (note some *relative* links are broken and the 1.5.0 directories are
>   not yet created - these will be OK once the site is deployed)
> 
>   Clirr Report (compared to 1.4.1):
> http://people.apache.org/~sebb/validator-1.5.0-RC1/clirr-report.html
> 
>   RAT Report:
> http://people.apache.org/~sebb/validator-1.5.0-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. after
> 10:00 GMT 22-Nov 2015
> 

I have first tested to build the site from the source archive using JDK
1.6, but it failed due to a problem with the used checkstyle plugin
(6.2). It obviously is compiled for Java 7 (class version 51).

This will certainly affect other components as well, but not a blocker
for the release imho.

Afterwards tested with JDK 1.7 and everything was fine.

There are a few checkstyle and findbugs errors which could be fixed as well.

[X] +1 Release these artifacts

Thomas

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

Re: Commons NoSQL

2015-11-22 Thread Gary Gregory 
OGM could work for log4j since we have known objects to marshall. I'll have
to study it and see if there is underlying API as generally usefull as JDBC.

Gary
On Nov 22, 2015 7:22 PM, "Yair Zaslavsky"  wrote:

> Hi Gary, I'm kinda n00b and really don't participate in the group , but
> isnt' there a project that is led by Emanuel Brenard about?
>
> http://hibernate.org/ogm/
>
> Is there going to be an adapter from OGM to your suggestion?
> How will you cope with the fact that there are several paradigms for no
> SQL?
> What about the trend of newSQL? Any thoughts here?
>
> Cheers,
> Yair
>
>
> On Mon, Nov 23, 2015 at 2:15 PM, Gary Gregory 
> wrote:
>
> > Any thoughts on creating a JDBC for NoSQL? Including modules for MongoDb
> > and CouchDb for example. Over at Log4j 2, we have a mini logging oriented
> > framework for NoSQL. The upshot would be to replace Log4j's NoSQL support
> > with Commons NoSQL.
> >
> > Gary
> >
>

Re: Proposed fluent string utils

2015-11-22 Thread Matt Benson 
On Nov 22, 2015 7:31 PM, "Henri Yandell"  wrote:
>
> My suggestion would be to add a link to teh Commons Lang website to
Micha's
> repo and see how successful it is (i.e. if successful, I'd expect to see
> users contributing other Lang related fluent APIs to it).
>
> I'd suggest renaming to fluengLang :)
>
I would add that I personally would have no problem with a compile time
only annotation dependency.

Matt

> On Mon, Nov 16, 2015 at 11:50 AM, Benedikt Ritter 
> wrote:
>
> > Hello again,
> >
> > 2015-11-16 20:22 GMT+01:00 Micha Pringle :
> >
> > > Hi Benedikt,
> > >
> > > Thanks for the reply.
> > >
> > > I will update the current code and make the following changes, then
> > notify
> > > the mail list when it is complete for further review.
> > > * Java 8 will be downgraded to Java 6. That's my own fault for unit
> > > testing with lambda's.
> > > * I would prefer to keep the annotations (especially the tiny
> > > net.jcip:jcip-annotations:1.0), but I will drop them and replace with
> > > javadoc.
> > > * I intended this to go into commons-lang3, I will look at BeanUtils2
and
> > > make the appropriate changes.
> > > * Since this idea looks like it will be included in Apache Commons
> > (lang3)
> > > I will review Java String and Guava String API's, to make sure
nothing is
> > > missed (and add unit tests). That seems unlikely though, StringUtils
> > seems
> > > to cover all the bases.
> > >
> >
> > I'm currently not convinced that this really belongs into Commons Lang.
> > Lang's description is "The standard Java libraries fail to provide
enough
> > methods for manipulation of its core classes. Apache Commons Lang
provides
> > these extra methods.". My opinion is, that we already have stuff in Lang
> > that isn't just auxiliary methods to the java.lang package. The change
you
> > propose looks like a fluent wrapper to java.lang.String, which while
> > generally useful does not feel like it belongs into Commons Lang. That's
> > why I've proposed to publish this as an additional package for
> > commons-lang3.
> >
> > If you would like to join development of Commons Lang, you can simply
go to
> > the bug tracker [1] and look through the open issues. To start working
on
> > open source projects, it's good to find small things to fix first. This
> > JavaDoc could be clearer, that test could be added, etc. This helps to
get
> > a general feeling for the library at hands, before tossing a big change
> > over with no discussion. It is very important for ASF projects to find
> > consensus in the community before changing code. So if you have an idea
> > which sounds good at the beginning, it may not fit into the project you
> > want to contribute it to. This doesn't make the idea less good, but it
may
> > lead to frustration if changes are not discussed at first.
> >
> > Having said this, I hope your not discouraged because I don't feel like
> > your FluentWrapper belongs into commons. We need people like you who are
> > enthusiastic! And by the way, I'm not the one to decide whether is will
be
> > added or not. I'm just sharing my thought. There may be other project
> > members you think this fits. It is still open for discussion.
> >
> >
> > >
> > > Without having yet looked at BeanUtils2 (so this might be a moot
> > > question), would it be useful to have a commons-lang3.fluent package
or
> > the
> > > like?
> > >
> >
> > I don't feel like "implementing fluent wrappers" is something that
belongs
> > into commons. There could be a commons-fluent component or something
like
> > that, which provides fluent wrappers for classes of the JDK. Given the
> > popularity of fluent APIs, this may be something others could have a
use of
> > as well.
> >
> >
> > >
> > > As for unit testing, do you want me to test all the delegating
methods as
> > > well? It seems like a lot of work for nominal gain.
> > >
> >
> > Changes should always be backed up by unit tests.
> >
> >
> > >
> > > Thanks again.
> > >
> >
> > Thank you for your interest in Apache Commons.
> >
> > Benedikt
> >
> > [1] http://issues.apache.org/jira/browse/LANG
> >
> >
> > >
> > > Cheers,
> > > Micha
> > > --
> > > *From:* Benedikt Ritter 
> > > *To:* Commons Developers List ; Micha Pringle
<
> > > michaprin...@yahoo.com>
> > > *Sent:* Monday, November 16, 2015 11:00 AM
> > > *Subject:* Re: Proposed fluent string utils
> > >
> > > Hello Micha,
> > >
> > > 2015-11-15 1:47 GMT+01:00 Micha Pringle
 > >:
> > >
> > >
> > > I really apologize, it seems the link below still managed to include a
> > > period despite my best efforts. Please tryhttps://
> > > github.com/michapringle/fluentStringUtils
> > >
> > > Cheers,Micha  From: Micha Pringle 
> > >  To: "dev@commons.apache.org" 
> > >  Sent: Saturday, November 14, 2015 4:44 PM
> > >  Subject:

Re: [VOTE] Release NET 3.4 based on RC2 - resend with corrected tag

2015-11-22 Thread Thomas Neidhart 
On 11/22/2015 04:58 PM, sebb wrote:
> It's probably about time to release NET.
> There have been quite a few improvements and fixes since the last version.
> 
> [This is a repeat of the original mail, but using a tag that actually
> exists this time]
> 
> ==
> 
> Net 3.4 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/net/ (svn revision 11241)
> 
> ./binaries/commons-net-3.4-bin.tar.gz.sha1:88411522395b4000b038a94ab007be89ebda2ec3
> ./binaries/commons-net-3.4-bin.zip.sha1:f252a45b1610346116c9dd966fec9a15171223d1
> ./source/commons-net-3.4-src.tar.gz.sha1:abfba84427a06341e113d59d8f75855e67093087
> ./source/commons-net-3.4-src.zip.sha1:f3b38dfcccd8fcdc9ac500a5f8580a19817b
> 
>   Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1120/commons-net/commons-net/3.4/
> 
> These are the artifacts and their hashes
> 
> /commons-net/commons-net/3.4/commons-net-3.4-test-sources.jar
> (SHA1: fdb74119054a2aacc134c56137660d7a0a40e4a8)
> /commons-net/commons-net/3.4/commons-net-3.4-javadoc.jar
> (SHA1: b882750c8dbd480e2b9afd357dcf71d962f2fa03)
> /commons-net/commons-net/3.4/commons-net-3.4-ftp.jar
> (SHA1: 6fc585e5f3dc8333b20110af22a8bae59f5246cb)
> /commons-net/commons-net/3.4/commons-net-3.4-tests.jar
> (SHA1: ce44ebc0e7be56c3bd650700be93c5b377b47573)
> /commons-net/commons-net/3.4/commons-net-3.4.pom
> (SHA1: d1790447a41c848af8cba0919fae7a577fbc744a)
> /commons-net/commons-net/3.4/commons-net-3.4.jar
> (SHA1: 5e984db9554728564d58e90da5d90eff8ae8cf2d)
> /commons-net/commons-net/3.4/commons-net-3.4-sources.jar
> (SHA1: 08439b8f20d7bdec502423732798a639501732c8)
> /commons-net/commons-net/3.4/commons-net-3.4-examples.jar
> (SHA1: 33abb13d790501fc9e4e77a40425bc381d39b9ca)
> 
>   Details of changes since 3.3 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/net/RELEASE-NOTES.txt
> http://people.apache.org/~sebb/net-3.4-RC2/changes-report.html
> 
>   I have tested this with JDK 1.6, 1.7, 1.8 using maven3.
> 
>   The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_4_RC2/
> (svn 1715635)
> 
>   N.B. the SVN revision is required because SVN tags are not immutable.
> 
>   Site:
> http://people.apache.org/~sebb/net-3.4-RC2/
>   (note some *relative* links are broken and the 3.4 directories are
>   not yet created - these will be OK once the site is deployed)
> 
>   download_net.cgi does not work, but the template can be checked at
> http://people.apache.org/~sebb/net-3.4-RC2/download_net.html
> 
>   Clirr Report (compared to 3.3):
> http://people.apache.org/~sebb/net-3.4-RC2/clirr-report.html
> 
>   Note that adding methods to an interface is binary-compatible, but
> not source-compatible
>   This change is documented in the Release Notes
> 
>   RAT Report:
> http://people.apache.org/~sebb/net-3.4-RC2/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. after
> 14:00 GMT 22-Nov 2015

Tested with JDK 1.7. Everything was running fine.

There are a few findbugs errors that could be fixed as well.

[X] +1 Release these artifacts

>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
>   Sebb
> 
> -
> 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: Proposed fluent string utils

2015-11-22 Thread Henri Yandell 
My suggestion would be to add a link to teh Commons Lang website to Micha's
repo and see how successful it is (i.e. if successful, I'd expect to see
users contributing other Lang related fluent APIs to it).

I'd suggest renaming to fluengLang :)

On Mon, Nov 16, 2015 at 11:50 AM, Benedikt Ritter 
wrote:

> Hello again,
>
> 2015-11-16 20:22 GMT+01:00 Micha Pringle :
>
> > Hi Benedikt,
> >
> > Thanks for the reply.
> >
> > I will update the current code and make the following changes, then
> notify
> > the mail list when it is complete for further review.
> > * Java 8 will be downgraded to Java 6. That's my own fault for unit
> > testing with lambda's.
> > * I would prefer to keep the annotations (especially the tiny
> > net.jcip:jcip-annotations:1.0), but I will drop them and replace with
> > javadoc.
> > * I intended this to go into commons-lang3, I will look at BeanUtils2 and
> > make the appropriate changes.
> > * Since this idea looks like it will be included in Apache Commons
> (lang3)
> > I will review Java String and Guava String API's, to make sure nothing is
> > missed (and add unit tests). That seems unlikely though, StringUtils
> seems
> > to cover all the bases.
> >
>
> I'm currently not convinced that this really belongs into Commons Lang.
> Lang's description is "The standard Java libraries fail to provide enough
> methods for manipulation of its core classes. Apache Commons Lang provides
> these extra methods.". My opinion is, that we already have stuff in Lang
> that isn't just auxiliary methods to the java.lang package. The change you
> propose looks like a fluent wrapper to java.lang.String, which while
> generally useful does not feel like it belongs into Commons Lang. That's
> why I've proposed to publish this as an additional package for
> commons-lang3.
>
> If you would like to join development of Commons Lang, you can simply go to
> the bug tracker [1] and look through the open issues. To start working on
> open source projects, it's good to find small things to fix first. This
> JavaDoc could be clearer, that test could be added, etc. This helps to get
> a general feeling for the library at hands, before tossing a big change
> over with no discussion. It is very important for ASF projects to find
> consensus in the community before changing code. So if you have an idea
> which sounds good at the beginning, it may not fit into the project you
> want to contribute it to. This doesn't make the idea less good, but it may
> lead to frustration if changes are not discussed at first.
>
> Having said this, I hope your not discouraged because I don't feel like
> your FluentWrapper belongs into commons. We need people like you who are
> enthusiastic! And by the way, I'm not the one to decide whether is will be
> added or not. I'm just sharing my thought. There may be other project
> members you think this fits. It is still open for discussion.
>
>
> >
> > Without having yet looked at BeanUtils2 (so this might be a moot
> > question), would it be useful to have a commons-lang3.fluent package or
> the
> > like?
> >
>
> I don't feel like "implementing fluent wrappers" is something that belongs
> into commons. There could be a commons-fluent component or something like
> that, which provides fluent wrappers for classes of the JDK. Given the
> popularity of fluent APIs, this may be something others could have a use of
> as well.
>
>
> >
> > As for unit testing, do you want me to test all the delegating methods as
> > well? It seems like a lot of work for nominal gain.
> >
>
> Changes should always be backed up by unit tests.
>
>
> >
> > Thanks again.
> >
>
> Thank you for your interest in Apache Commons.
>
> Benedikt
>
> [1] http://issues.apache.org/jira/browse/LANG
>
>
> >
> > Cheers,
> > Micha
> > --
> > *From:* Benedikt Ritter 
> > *To:* Commons Developers List ; Micha Pringle <
> > michaprin...@yahoo.com>
> > *Sent:* Monday, November 16, 2015 11:00 AM
> > *Subject:* Re: Proposed fluent string utils
> >
> > Hello Micha,
> >
> > 2015-11-15 1:47 GMT+01:00 Micha Pringle  >:
> >
> >
> > I really apologize, it seems the link below still managed to include a
> > period despite my best efforts. Please tryhttps://
> > github.com/michapringle/fluentStringUtils
> >
> > Cheers,Micha  From: Micha Pringle 
> >  To: "dev@commons.apache.org" 
> >  Sent: Saturday, November 14, 2015 4:44 PM
> >  Subject: Proposed fluent string utils
> >
> > Hi folks,
> >
> > Firstly, apologies if this results in a double post. I tried posting a
> > couple of times, but the first time I sent to the user list (sorry), and
> > the second time I do not see my email at all in the mail archive (
> > http://mail-archives.apache.org/mod_mbox/commons-dev/201511.mbox/thread
> ).
> > Hopefully 3rd time is the charm, and again, sorry for my

Commons NoSQL

2015-11-22 Thread Gary Gregory 
Any thoughts on creating a JDBC for NoSQL? Including modules for MongoDb
and CouchDb for example. Over at Log4j 2, we have a mini logging oriented
framework for NoSQL. The upshot would be to replace Log4j's NoSQL support
with Commons NoSQL.

Gary

Re: Commons NoSQL

2015-11-22 Thread Yair Zaslavsky 
Hi Gary, I'm kinda n00b and really don't participate in the group , but
isnt' there a project that is led by Emanuel Brenard about?

http://hibernate.org/ogm/

Is there going to be an adapter from OGM to your suggestion?
How will you cope with the fact that there are several paradigms for no SQL?
What about the trend of newSQL? Any thoughts here?

Cheers,
Yair


On Mon, Nov 23, 2015 at 2:15 PM, Gary Gregory 
wrote:

> Any thoughts on creating a JDBC for NoSQL? Including modules for MongoDb
> and CouchDb for example. Over at Log4j 2, we have a mini logging oriented
> framework for NoSQL. The upshot would be to replace Log4j's NoSQL support
> with Commons NoSQL.
>
> Gary
>

Re: [JXPATH] Java Version

2015-11-22 Thread Benedikt Ritter 
I'm fine with Java 7, since Java 6 has already reached EOL.

2015-11-21 19:48 GMT+01:00 Gary Gregory :

> I'd go with Java 7.
>
> Gary
> On Nov 21, 2015 3:50 AM, "Benedikt Ritter"  wrote:
>
> > Hi,
> >
> > any preference on which Java Version JXPath 1.4 target? Currently the
> build
> > is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
> machine,
> > so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
> see
> > a reason to keep support for such old Java versions.
> >
> > Thoughts?
> > Benedikt
> >
> > --
> > http://people.apache.org/~britter/
> > http://www.systemoutprintln.de/
> > http://twitter.com/BenediktRitter
> > http://github.com/britter
> >
>



-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter

Re: [RESULT] [VOTE] Accept Naomi

2015-11-22 Thread Dave Brosius 

Folks,

I take it from our collective lack of movement, that we are voting no, 
and just not willing to say it. If that is the case, we should have the 
courtesy to say no, and at least give closure.


dave

On 11/08/2015 02:14 PM, Dave Brosius wrote:
I have already merged the changes into master, and deleted the 
gh-pages branch here


https://github.com/mebigfatguy/Naomi


I can add a pull request to Norm to accept these in his repository, if 
you like.



On 11/08/2015 01:53 PM, Bernd Eckenfels wrote:

Phil:

I am not happy about proceeding, though, in the presence of the

-1

votes.  We like to make decisions by consensus and while this is a
procedural decision and therefore subject to majority approval, I
would like to ask those who case negative votes to reconsider.

I have an counter proposal: how about addressing most of the concerns
first:

- merge the mavenisation cleanly, it is not asked too much to display
   it in master not gh-pages
- add some samples to the readme
- adopt commons codestyle

If those 3 things are done by the submitters I personally would be very
reliefed (I still would not see a case to use it myself, but at least
we wont have any ground for the rockstar argument anymore). I am not
sure about the "incubator" argument, as I understood it, it is not
needed for IP clearance.

And given the vote already passed you can just make the above clean-up
in git(hub) and get it merged to the sandbox.

gruss
Bernd

-
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: [JXPATH] Java Version

2015-11-22 Thread Dave Brosius 

As has java 7 reached end of life.

On 11/22/2015 09:06 AM, Benedikt Ritter wrote:

I'm fine with Java 7, since Java 6 has already reached EOL.

2015-11-21 19:48 GMT+01:00 Gary Gregory :


I'd go with Java 7.

Gary
On Nov 21, 2015 3:50 AM, "Benedikt Ritter"  wrote:


Hi,

any preference on which Java Version JXPath 1.4 target? Currently the

build

is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my

machine,

so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't

see

a reason to keep support for such old Java versions.

Thoughts?
Benedikt

--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter







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

Re: [JXPATH] Java Version

2015-11-22 Thread sebb 
Java 7 seems OK to me, though if the code builds and test OK with Java
1.6, why not leave it at that?

Just because Java 1.6 is EOL does not mean that Java 1.6-compatible
code will stop working.

So long as the Java runtime used to run the code is updated to a
currently supported version of Java, that is enough to ensure that any
JVM bugs are fixed.


On 22 November 2015 at 15:19, James Ring  wrote:
> Unfortunately Android still uses Java 7, if you want Android
> developers to be able to use the library then I think you should
> target 7.
>
> On Sun, Nov 22, 2015 at 7:12 AM, Benedikt Ritter  wrote:
>> Okay, so we go with Java 8? Doesn't feel like it has reached enough market
>> penetration yet. But I don't know numbers about that.
>>
>> 2015-11-22 15:20 GMT+01:00 Dave Brosius :
>>
>>> As has java 7 reached end of life.
>>>
>>> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
>>>
 I'm fine with Java 7, since Java 6 has already reached EOL.

 2015-11-21 19:48 GMT+01:00 Gary Gregory :

 I'd go with Java 7.
>
> Gary
> On Nov 21, 2015 3:50 AM, "Benedikt Ritter"  wrote:
>
> Hi,
>>
>> any preference on which Java Version JXPath 1.4 target? Currently the
>>
> build
>
>> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
>>
> machine,
>
>> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
>>
> see
>
>> a reason to keep support for such old Java versions.
>>
>> Thoughts?
>> Benedikt
>>
>> --
>> http://people.apache.org/~britter/
>> http://www.systemoutprintln.de/
>> http://twitter.com/BenediktRitter
>> http://github.com/britter
>>
>>


>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>>
>>
>> --
>> http://people.apache.org/~britter/
>> http://www.systemoutprintln.de/
>> http://twitter.com/BenediktRitter
>> http://github.com/britter
>
> -
> 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: [JXPATH] Java Version

2015-11-22 Thread Gary Gregory 
On Sun, Nov 22, 2015 at 6:20 AM, Dave Brosius  wrote:

> As has java 7 reached end of life.


FYI: I think IBM still supports their Java 7 IIRC

Gayr

>
>
> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
>
>> I'm fine with Java 7, since Java 6 has already reached EOL.
>>
>> 2015-11-21 19:48 GMT+01:00 Gary Gregory :
>>
>> I'd go with Java 7.
>>>
>>> Gary
>>> On Nov 21, 2015 3:50 AM, "Benedikt Ritter"  wrote:
>>>
>>> Hi,

 any preference on which Java Version JXPath 1.4 target? Currently the

>>> build
>>>
 is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my

>>> machine,
>>>
 so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't

>>> see
>>>
 a reason to keep support for such old Java versions.

 Thoughts?
 Benedikt

 --
 http://people.apache.org/~britter/
 http://www.systemoutprintln.de/
 http://twitter.com/BenediktRitter
 http://github.com/britter


>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-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: [JXPATH] Java Version

2015-11-22 Thread Benedikt Ritter 
Okay, so we go with Java 8? Doesn't feel like it has reached enough market
penetration yet. But I don't know numbers about that.

2015-11-22 15:20 GMT+01:00 Dave Brosius :

> As has java 7 reached end of life.
>
> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
>
>> I'm fine with Java 7, since Java 6 has already reached EOL.
>>
>> 2015-11-21 19:48 GMT+01:00 Gary Gregory :
>>
>> I'd go with Java 7.
>>>
>>> Gary
>>> On Nov 21, 2015 3:50 AM, "Benedikt Ritter"  wrote:
>>>
>>> Hi,

 any preference on which Java Version JXPath 1.4 target? Currently the

>>> build
>>>
 is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my

>>> machine,
>>>
 so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't

>>> see
>>>
 a reason to keep support for such old Java versions.

 Thoughts?
 Benedikt

 --
 http://people.apache.org/~britter/
 http://www.systemoutprintln.de/
 http://twitter.com/BenediktRitter
 http://github.com/britter


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


-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter

Re: [JXPATH] Java Version

2015-11-22 Thread James Ring 
Unfortunately Android still uses Java 7, if you want Android
developers to be able to use the library then I think you should
target 7.

On Sun, Nov 22, 2015 at 7:12 AM, Benedikt Ritter  wrote:
> Okay, so we go with Java 8? Doesn't feel like it has reached enough market
> penetration yet. But I don't know numbers about that.
>
> 2015-11-22 15:20 GMT+01:00 Dave Brosius :
>
>> As has java 7 reached end of life.
>>
>> On 11/22/2015 09:06 AM, Benedikt Ritter wrote:
>>
>>> I'm fine with Java 7, since Java 6 has already reached EOL.
>>>
>>> 2015-11-21 19:48 GMT+01:00 Gary Gregory :
>>>
>>> I'd go with Java 7.

 Gary
 On Nov 21, 2015 3:50 AM, "Benedikt Ritter"  wrote:

 Hi,
>
> any preference on which Java Version JXPath 1.4 target? Currently the
>
 build

> is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my
>
 machine,

> so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't
>
 see

> a reason to keep support for such old Java versions.
>
> Thoughts?
> Benedikt
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>
>
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter

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

Re: [RESULT] [VOTE] Accept Naomi

2015-11-22 Thread Gary Gregory 
The person who called the VOTE should tally it up and report here.

Gary

On Sun, Nov 22, 2015 at 6:14 AM, Dave Brosius  wrote:

> Folks,
>
> I take it from our collective lack of movement, that we are voting no, and
> just not willing to say it. If that is the case, we should have the
> courtesy to say no, and at least give closure.
>
> dave
>
> On 11/08/2015 02:14 PM, Dave Brosius wrote:
>
>> I have already merged the changes into master, and deleted the gh-pages
>> branch here
>>
>> https://github.com/mebigfatguy/Naomi
>>
>>
>> I can add a pull request to Norm to accept these in his repository, if
>> you like.
>>
>>
>> On 11/08/2015 01:53 PM, Bernd Eckenfels wrote:
>>
>>> Phil:
>>>
 I am not happy about proceeding, though, in the presence of the

>>> -1
>>>
 votes.  We like to make decisions by consensus and while this is a
 procedural decision and therefore subject to majority approval, I
 would like to ask those who case negative votes to reconsider.

>>> I have an counter proposal: how about addressing most of the concerns
>>> first:
>>>
>>> - merge the mavenisation cleanly, it is not asked too much to display
>>>it in master not gh-pages
>>> - add some samples to the readme
>>> - adopt commons codestyle
>>>
>>> If those 3 things are done by the submitters I personally would be very
>>> reliefed (I still would not see a case to use it myself, but at least
>>> we wont have any ground for the rockstar argument anymore). I am not
>>> sure about the "incubator" argument, as I understood it, it is not
>>> needed for IP clearance.
>>>
>>> And given the vote already passed you can just make the above clean-up
>>> in git(hub) and get it merged to the sandbox.
>>>
>>> gruss
>>> Bernd
>>>
>>> -
>>> 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
>
>


-- 
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

[CANCELLED][VOTE] Release NET 3.4 based on RC2

2015-11-22 Thread sebb 
I overlooked a file when creating RC1, so I abandoned that, but I did
not yet delete the tag.

Unfortunately when I created the tag for RC2, it was created under validator:

https://svn.apache.org/repos/asf/commons/proper/validator/tags/NET_3_4_RC2/

The NET tag

http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_4_RC2/

does not actually exist.

I need to restart the release vote with a valid tag.

Sorry for the confusion.


On 21 November 2015 at 15:38, Benedikt Ritter  wrote:
> Hello sebb,
>
> I'm getting a difference when comparing the src archive with the tag:
>
> $ diff -rwq commons-net-3.4-src NET_3_4_RC1/
> Only in NET_3_4_RC1/: .svn
> Only in NET_3_4_RC1/: doap_net.rdf

The doap does not belong in the source archive.

> Files
> commons-net-3.4-src/src/test/java/org/apache/commons/net/smtp/SimpleSMTPHeaderTestCase.java
> and
> NET_3_4_RC1/src/test/java/org/apache/commons/net/smtp/SimpleSMTPHeaderTestCase.java
> differ
>
> looks like something related to line breaks. Don't know why it only shows
> up for SimpleSMTPHeaderTestCase.

Wrong tag for comparison; see above.

> Everything else looks good to me. I've build with Java 6,7 and 8. Net 3.4
> can not be build with Java 9 EA because source option 1.5 has been removed.
>
> +1
>
> Benedikt
>
> 2015-11-19 14:09 GMT+01:00 sebb :
>
>> It's probably about time to release NET.
>> There have been quite a few improvements and fixes since the last version.
>>
>> ==
>>
>> Net 3.4 RC2 is available for review here:
>> https://dist.apache.org/repos/dist/dev/commons/net/ (svn revision
>> 11241)
>>
>>
>> ./binaries/commons-net-3.4-bin.tar.gz.sha1:88411522395b4000b038a94ab007be89ebda2ec3
>>
>> ./binaries/commons-net-3.4-bin.zip.sha1:f252a45b1610346116c9dd966fec9a15171223d1
>>
>> ./source/commons-net-3.4-src.tar.gz.sha1:abfba84427a06341e113d59d8f75855e67093087
>>
>> ./source/commons-net-3.4-src.zip.sha1:f3b38dfcccd8fcdc9ac500a5f8580a19817b
>>
>>   Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1120/commons-net/commons-net/3.4/
>>
>> These are the artifacts and their hashes
>>
>> /commons-net/commons-net/3.4/commons-net-3.4-test-sources.jar
>> (SHA1: fdb74119054a2aacc134c56137660d7a0a40e4a8)
>> /commons-net/commons-net/3.4/commons-net-3.4-javadoc.jar
>> (SHA1: b882750c8dbd480e2b9afd357dcf71d962f2fa03)
>> /commons-net/commons-net/3.4/commons-net-3.4-ftp.jar
>> (SHA1: 6fc585e5f3dc8333b20110af22a8bae59f5246cb)
>> /commons-net/commons-net/3.4/commons-net-3.4-tests.jar
>> (SHA1: ce44ebc0e7be56c3bd650700be93c5b377b47573)
>> /commons-net/commons-net/3.4/commons-net-3.4.pom
>> (SHA1: d1790447a41c848af8cba0919fae7a577fbc744a)
>> /commons-net/commons-net/3.4/commons-net-3.4.jar
>> (SHA1: 5e984db9554728564d58e90da5d90eff8ae8cf2d)
>> /commons-net/commons-net/3.4/commons-net-3.4-sources.jar
>> (SHA1: 08439b8f20d7bdec502423732798a639501732c8)
>> /commons-net/commons-net/3.4/commons-net-3.4-examples.jar
>> (SHA1: 33abb13d790501fc9e4e77a40425bc381d39b9ca)
>>
>>   Details of changes since 3.3 are in the release notes:
>> https://dist.apache.org/repos/dist/dev/commons/net/RELEASE-NOTES.txt
>> http://people.apache.org/~sebb/net-3.4-RC2/changes-report.html
>>
>>   I have tested this with JDK 1.6, 1.7, 1.8 using maven3.
>>
>>   The tag is here:
>> http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_4_RC2/
>> (svn 1715166)
>>   N.B. the SVN revision is required because SVN tags are not immutable.
>>
>>   Site:
>> http://people.apache.org/~sebb/net-3.4-RC2/
>>   (note some *relative* links are broken and the 3.4 directories are
>>   not yet created - these will be OK once the site is deployed)
>>
>>   download_net.cgi does not work, but the template can be checked at
>> http://people.apache.org/~sebb/net-3.4-RC2/download_net.html
>>
>>   Clirr Report (compared to 3.3):
>> http://people.apache.org/~sebb/net-3.4-RC2/clirr-report.html
>>
>>   Note that adding methods to an interface is binary-compatible, but
>> not source-compatible
>>   This change is documented in the Release Notes
>>
>>   RAT Report:
>> http://people.apache.org/~sebb/net-3.4-RC2/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. after
>> 14:00 GMT 22-Nov 2015
>>
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>>
>>   Thanks!
>>
>>   Sebb
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter

[VOTE] Release NET 3.4 based on RC2 - resend with corrected tag

2015-11-22 Thread sebb 
It's probably about time to release NET.
There have been quite a few improvements and fixes since the last version.

[This is a repeat of the original mail, but using a tag that actually
exists this time]

==

Net 3.4 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/net/ (svn revision 11241)

./binaries/commons-net-3.4-bin.tar.gz.sha1:88411522395b4000b038a94ab007be89ebda2ec3
./binaries/commons-net-3.4-bin.zip.sha1:f252a45b1610346116c9dd966fec9a15171223d1
./source/commons-net-3.4-src.tar.gz.sha1:abfba84427a06341e113d59d8f75855e67093087
./source/commons-net-3.4-src.zip.sha1:f3b38dfcccd8fcdc9ac500a5f8580a19817b

  Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1120/commons-net/commons-net/3.4/

These are the artifacts and their hashes

/commons-net/commons-net/3.4/commons-net-3.4-test-sources.jar
(SHA1: fdb74119054a2aacc134c56137660d7a0a40e4a8)
/commons-net/commons-net/3.4/commons-net-3.4-javadoc.jar
(SHA1: b882750c8dbd480e2b9afd357dcf71d962f2fa03)
/commons-net/commons-net/3.4/commons-net-3.4-ftp.jar
(SHA1: 6fc585e5f3dc8333b20110af22a8bae59f5246cb)
/commons-net/commons-net/3.4/commons-net-3.4-tests.jar
(SHA1: ce44ebc0e7be56c3bd650700be93c5b377b47573)
/commons-net/commons-net/3.4/commons-net-3.4.pom
(SHA1: d1790447a41c848af8cba0919fae7a577fbc744a)
/commons-net/commons-net/3.4/commons-net-3.4.jar
(SHA1: 5e984db9554728564d58e90da5d90eff8ae8cf2d)
/commons-net/commons-net/3.4/commons-net-3.4-sources.jar
(SHA1: 08439b8f20d7bdec502423732798a639501732c8)
/commons-net/commons-net/3.4/commons-net-3.4-examples.jar
(SHA1: 33abb13d790501fc9e4e77a40425bc381d39b9ca)

  Details of changes since 3.3 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/net/RELEASE-NOTES.txt
http://people.apache.org/~sebb/net-3.4-RC2/changes-report.html

  I have tested this with JDK 1.6, 1.7, 1.8 using maven3.

  The tag is here:
http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_4_RC2/
(svn 1715635)

  N.B. the SVN revision is required because SVN tags are not immutable.

  Site:
http://people.apache.org/~sebb/net-3.4-RC2/
  (note some *relative* links are broken and the 3.4 directories are
  not yet created - these will be OK once the site is deployed)

  download_net.cgi does not work, but the template can be checked at
http://people.apache.org/~sebb/net-3.4-RC2/download_net.html

  Clirr Report (compared to 3.3):
http://people.apache.org/~sebb/net-3.4-RC2/clirr-report.html

  Note that adding methods to an interface is binary-compatible, but
not source-compatible
  This change is documented in the Release Notes

  RAT Report:
http://people.apache.org/~sebb/net-3.4-RC2/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. after
14:00 GMT 22-Nov 2015

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

  Thanks!

  Sebb

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

Re: [VOTE] Release Validator 1.5.0 based on RC1

2015-11-22 Thread Gary Gregory 
Oh, I forgot to say that the build fails with Java 8 due to the usual
Javadoc failures but it was fine with my main platform:

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T08:41:47-08:00)
Maven home: E:\Java\apache-maven-3.3.9\bin\..
Java version: 1.7.0_79, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_79\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

Gary

On Sun, Nov 22, 2015 at 10:21 AM, Gary Gregory 
wrote:

> +1
>
> From src zip, builds OK, reports OK (Clirr, RAT), ASC OK, SHA1 OK, MD5 OK.
>
> We should really fix some of the FindBugs but there are no blockers.
>
> Gary
>
> On Thu, Nov 19, 2015 at 1:48 AM, sebb  wrote:
>
>> It's probably about time to release VALIDATOR.
>> There have been quite a few improvements and fixes since the last version.
>>
>> ==
>>
>> Validator 1.5.0 RC1 is available for review here:
>> https://dist.apache.org/repos/dist/dev/commons/validator/ (svn
>> revision 11236)
>>
>>
>> ./binaries/commons-validator-1.5.0-bin.tar.gz.sha1:d1ec43eee78475675787db4ce478f03e9089a38f
>>
>> ./binaries/commons-validator-1.5.0-bin.zip.sha1:de3664516fdf68667d10b8d060eebd0cf1e349c5
>>
>> ./source/commons-validator-1.5.0-src.tar.gz.sha1:737f4df692f3d64bd8c0c6ba6c39e1a7533309c0
>>
>> ./source/commons-validator-1.5.0-src.zip.sha1:690c353b52359e75a6b5f0bd1b0cf0f34067c544
>>
>>   Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1118/commons-validator/commons-validator/1.5.0/
>>
>> These are the artifacts and their hashes
>>
>>
>> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-tests.jar
>> (SHA1: 371f755d033b4a5d4a8b799e453e27e8211179a7)
>> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0.pom
>> (SHA1: 4050c881a79cd5e621339c749ef03b47eb851a4a)
>> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0.jar
>> (SHA1: 26b98c21975c5caf6bf34bacdeb7183be7a65970)
>>
>> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-javadoc.jar
>> (SHA1: f3f3364cb4b3e9d9b0362b2bb2770a579ec76a64)
>>
>> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-sources.jar
>> (SHA1: 96c77b61d4ed9ca3b58a7a40bac7fa98a09f5c2f)
>>
>> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-test-sources.jar
>> (SHA1: 68e7c52affe4fdc98d4431e6b9ffcc30969279a1)
>>
>>   Details of changes since 1.4.1 are in the release notes:
>>
>> https://dist.apache.org/repos/dist/dev/commons/validator/RELEASE-NOTES.txt
>>
>> http://people.apache.org/~sebb/validator-1.5.0-RC1/changes-report.html
>>
>>   I have tested this with JDK 1.6, 1.7, 1.8 using maven3.
>>
>>   The tag is here:
>>
>> http://svn.apache.org/repos/asf/commons/proper/validator/tags/VALIDATOR_1_5_0_RC1/
>> (svn 1715135)
>>   N.B. the SVN revision is required because SVN tags are not immutable.
>>
>>   Site:
>> http://people.apache.org/~sebb/validator-1.5.0-RC1/
>>   (note some *relative* links are broken and the 1.5.0 directories are
>>   not yet created - these will be OK once the site is deployed)
>>
>>   Clirr Report (compared to 1.4.1):
>> http://people.apache.org/~sebb/validator-1.5.0-RC1/clirr-report.html
>>
>>   RAT Report:
>> http://people.apache.org/~sebb/validator-1.5.0-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. after
>> 10:00 GMT 22-Nov 2015
>>
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>>
>>   Thanks!
>>
>>   Sebb
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-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
>



-- 
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] Release Validator 1.5.0 based on RC1

2015-11-22 Thread Gary Gregory 
+1

>From src zip, builds OK, reports OK (Clirr, RAT), ASC OK, SHA1 OK, MD5 OK.

We should really fix some of the FindBugs but there are no blockers.

Gary

On Thu, Nov 19, 2015 at 1:48 AM, sebb  wrote:

> It's probably about time to release VALIDATOR.
> There have been quite a few improvements and fixes since the last version.
>
> ==
>
> Validator 1.5.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/validator/ (svn
> revision 11236)
>
>
> ./binaries/commons-validator-1.5.0-bin.tar.gz.sha1:d1ec43eee78475675787db4ce478f03e9089a38f
>
> ./binaries/commons-validator-1.5.0-bin.zip.sha1:de3664516fdf68667d10b8d060eebd0cf1e349c5
>
> ./source/commons-validator-1.5.0-src.tar.gz.sha1:737f4df692f3d64bd8c0c6ba6c39e1a7533309c0
>
> ./source/commons-validator-1.5.0-src.zip.sha1:690c353b52359e75a6b5f0bd1b0cf0f34067c544
>
>   Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1118/commons-validator/commons-validator/1.5.0/
>
> These are the artifacts and their hashes
>
>
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-tests.jar
> (SHA1: 371f755d033b4a5d4a8b799e453e27e8211179a7)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0.pom
> (SHA1: 4050c881a79cd5e621339c749ef03b47eb851a4a)
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0.jar
> (SHA1: 26b98c21975c5caf6bf34bacdeb7183be7a65970)
>
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-javadoc.jar
> (SHA1: f3f3364cb4b3e9d9b0362b2bb2770a579ec76a64)
>
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-sources.jar
> (SHA1: 96c77b61d4ed9ca3b58a7a40bac7fa98a09f5c2f)
>
> /commons-validator/commons-validator/1.5.0/commons-validator-1.5.0-test-sources.jar
> (SHA1: 68e7c52affe4fdc98d4431e6b9ffcc30969279a1)
>
>   Details of changes since 1.4.1 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/validator/RELEASE-NOTES.txt
> http://people.apache.org/~sebb/validator-1.5.0-RC1/changes-report.html
>
>   I have tested this with JDK 1.6, 1.7, 1.8 using maven3.
>
>   The tag is here:
>
> http://svn.apache.org/repos/asf/commons/proper/validator/tags/VALIDATOR_1_5_0_RC1/
> (svn 1715135)
>   N.B. the SVN revision is required because SVN tags are not immutable.
>
>   Site:
> http://people.apache.org/~sebb/validator-1.5.0-RC1/
>   (note some *relative* links are broken and the 1.5.0 directories are
>   not yet created - these will be OK once the site is deployed)
>
>   Clirr Report (compared to 1.4.1):
> http://people.apache.org/~sebb/validator-1.5.0-RC1/clirr-report.html
>
>   RAT Report:
> http://people.apache.org/~sebb/validator-1.5.0-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. after
> 10:00 GMT 22-Nov 2015
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
>   Thanks!
>
>   Sebb
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-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: [RESULT] [VOTE] Accept Naomi

2015-11-22 Thread Gary Gregory 
On Sun, Nov 22, 2015 at 9:51 AM, Phil Steitz  wrote:

> On 11/22/15 8:47 AM, Gary Gregory wrote:
> > The person who called the VOTE should tally it up and report here.
>
> I did tally the VOTE.  We had three -1 PMC Votes.  I asked the -1s
> to reconsider and they did not change their votes. Technically, we
> could call it a pass and push forward, but I was not personally
> prepared to do that.  I concluded that we did not have consensus to
> move forward directly into the Sandbox.  I also stated that I do not
> have the cycles at this time to rejoin the Incubator PMC and
> initiate the process there.  If someone else wants to do that,
> fine.  Bottom line is the direct-to-sandbox approach failed to
> achieve consensus and we need someone to volunteer to take on the
> Incubator process for this if we want to get this code into Commons.
>

Thanks for the refresher.

Gary


>
> Phil
> >
> > Gary
> >
> > On Sun, Nov 22, 2015 at 6:14 AM, Dave Brosius 
> wrote:
> >
> >> Folks,
> >>
> >> I take it from our collective lack of movement, that we are voting no,
> and
> >> just not willing to say it. If that is the case, we should have the
> >> courtesy to say no, and at least give closure.
> >>
> >> dave
> >>
> >> On 11/08/2015 02:14 PM, Dave Brosius wrote:
> >>
> >>> I have already merged the changes into master, and deleted the gh-pages
> >>> branch here
> >>>
> >>> https://github.com/mebigfatguy/Naomi
> >>>
> >>>
> >>> I can add a pull request to Norm to accept these in his repository, if
> >>> you like.
> >>>
> >>>
> >>> On 11/08/2015 01:53 PM, Bernd Eckenfels wrote:
> >>>
>  Phil:
> 
> > I am not happy about proceeding, though, in the presence of the
> >
>  -1
> 
> > votes.  We like to make decisions by consensus and while this is a
> > procedural decision and therefore subject to majority approval, I
> > would like to ask those who case negative votes to reconsider.
> >
>  I have an counter proposal: how about addressing most of the concerns
>  first:
> 
>  - merge the mavenisation cleanly, it is not asked too much to display
> it in master not gh-pages
>  - add some samples to the readme
>  - adopt commons codestyle
> 
>  If those 3 things are done by the submitters I personally would be
> very
>  reliefed (I still would not see a case to use it myself, but at least
>  we wont have any ground for the rockstar argument anymore). I am not
>  sure about the "incubator" argument, as I understood it, it is not
>  needed for IP clearance.
> 
>  And given the vote already passed you can just make the above clean-up
>  in git(hub) and get it merged to the sandbox.
> 
>  gruss
>  Bernd
> 
>  -
>  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
> >>
> >>
> >
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-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: [JXPATH] Java Version

2015-11-22 Thread Pascal Schumacher 

If you pay Oracle for long term support you still get updates for Java 7.

This means that there will be some people (like me at work :() which 
have to stick to Java 7 for some time.


Am 22.11.2015 um 16:44 schrieb Gary Gregory:

On Sun, Nov 22, 2015 at 6:20 AM, Dave Brosius  wrote:


As has java 7 reached end of life.


FYI: I think IBM still supports their Java 7 IIRC

Gayr



On 11/22/2015 09:06 AM, Benedikt Ritter wrote:


I'm fine with Java 7, since Java 6 has already reached EOL.

2015-11-21 19:48 GMT+01:00 Gary Gregory :

I'd go with Java 7.

Gary
On Nov 21, 2015 3:50 AM, "Benedikt Ritter"  wrote:

Hi,

any preference on which Java Version JXPath 1.4 target? Currently the


build


is set to 1.3. I've only Java 1.6, 1.7 1.8 and 1.9 installed on my


machine,


so I won't be able to test with 1.3, 1.4 and 1.5. Further more I don't


see


a reason to keep support for such old Java versions.

Thoughts?
Benedikt

--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter





-
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 NET 3.4 based on RC2 - resend with corrected tag

2015-11-22 Thread Oliver Heger 
Build works fine for me with Java 1.5 and Java 1.8 on Windows 10.
Artifacts and site look good. So +1.

Interestingly, when I build the site locally my clirr report shows 12
errors. In addition to the 3 errors about methods added to an interface,
I also get a bunch of errors about public methods which are now final,
for instance:

* public org.apache.commons.net.ftp.FTPCmd[] values()
* public org.apache.commons.net.imap.IMAP$IMAPState[] values()
* public org.apache.commons.net.imap.IMAPClient$SEARCH_CRITERIA[] values()

These are all enum classes, so the message is pretty pointless. Maybe a
Java 8 issue?

Oliver

Am 22.11.2015 um 16:58 schrieb sebb:
> It's probably about time to release NET.
> There have been quite a few improvements and fixes since the last version.
> 
> [This is a repeat of the original mail, but using a tag that actually
> exists this time]
> 
> ==
> 
> Net 3.4 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/net/ (svn revision 11241)
> 
> ./binaries/commons-net-3.4-bin.tar.gz.sha1:88411522395b4000b038a94ab007be89ebda2ec3
> ./binaries/commons-net-3.4-bin.zip.sha1:f252a45b1610346116c9dd966fec9a15171223d1
> ./source/commons-net-3.4-src.tar.gz.sha1:abfba84427a06341e113d59d8f75855e67093087
> ./source/commons-net-3.4-src.zip.sha1:f3b38dfcccd8fcdc9ac500a5f8580a19817b
> 
>   Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1120/commons-net/commons-net/3.4/
> 
> These are the artifacts and their hashes
> 
> /commons-net/commons-net/3.4/commons-net-3.4-test-sources.jar
> (SHA1: fdb74119054a2aacc134c56137660d7a0a40e4a8)
> /commons-net/commons-net/3.4/commons-net-3.4-javadoc.jar
> (SHA1: b882750c8dbd480e2b9afd357dcf71d962f2fa03)
> /commons-net/commons-net/3.4/commons-net-3.4-ftp.jar
> (SHA1: 6fc585e5f3dc8333b20110af22a8bae59f5246cb)
> /commons-net/commons-net/3.4/commons-net-3.4-tests.jar
> (SHA1: ce44ebc0e7be56c3bd650700be93c5b377b47573)
> /commons-net/commons-net/3.4/commons-net-3.4.pom
> (SHA1: d1790447a41c848af8cba0919fae7a577fbc744a)
> /commons-net/commons-net/3.4/commons-net-3.4.jar
> (SHA1: 5e984db9554728564d58e90da5d90eff8ae8cf2d)
> /commons-net/commons-net/3.4/commons-net-3.4-sources.jar
> (SHA1: 08439b8f20d7bdec502423732798a639501732c8)
> /commons-net/commons-net/3.4/commons-net-3.4-examples.jar
> (SHA1: 33abb13d790501fc9e4e77a40425bc381d39b9ca)
> 
>   Details of changes since 3.3 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/net/RELEASE-NOTES.txt
> http://people.apache.org/~sebb/net-3.4-RC2/changes-report.html
> 
>   I have tested this with JDK 1.6, 1.7, 1.8 using maven3.
> 
>   The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_4_RC2/
> (svn 1715635)
> 
>   N.B. the SVN revision is required because SVN tags are not immutable.
> 
>   Site:
> http://people.apache.org/~sebb/net-3.4-RC2/
>   (note some *relative* links are broken and the 3.4 directories are
>   not yet created - these will be OK once the site is deployed)
> 
>   download_net.cgi does not work, but the template can be checked at
> http://people.apache.org/~sebb/net-3.4-RC2/download_net.html
> 
>   Clirr Report (compared to 3.3):
> http://people.apache.org/~sebb/net-3.4-RC2/clirr-report.html
> 
>   Note that adding methods to an interface is binary-compatible, but
> not source-compatible
>   This change is documented in the Release Notes
> 
>   RAT Report:
> http://people.apache.org/~sebb/net-3.4-RC2/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. after
> 14:00 GMT 22-Nov 2015
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 
>   Sebb
> 
> -
> 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: [RESULT] [VOTE] Accept Naomi

2015-11-22 Thread Phil Steitz 
On 11/22/15 8:47 AM, Gary Gregory wrote:
> The person who called the VOTE should tally it up and report here.

I did tally the VOTE.  We had three -1 PMC Votes.  I asked the -1s
to reconsider and they did not change their votes. Technically, we
could call it a pass and push forward, but I was not personally
prepared to do that.  I concluded that we did not have consensus to
move forward directly into the Sandbox.  I also stated that I do not
have the cycles at this time to rejoin the Incubator PMC and
initiate the process there.  If someone else wants to do that,
fine.  Bottom line is the direct-to-sandbox approach failed to
achieve consensus and we need someone to volunteer to take on the
Incubator process for this if we want to get this code into Commons.

Phil
>
> Gary
>
> On Sun, Nov 22, 2015 at 6:14 AM, Dave Brosius  wrote:
>
>> Folks,
>>
>> I take it from our collective lack of movement, that we are voting no, and
>> just not willing to say it. If that is the case, we should have the
>> courtesy to say no, and at least give closure.
>>
>> dave
>>
>> On 11/08/2015 02:14 PM, Dave Brosius wrote:
>>
>>> I have already merged the changes into master, and deleted the gh-pages
>>> branch here
>>>
>>> https://github.com/mebigfatguy/Naomi
>>>
>>>
>>> I can add a pull request to Norm to accept these in his repository, if
>>> you like.
>>>
>>>
>>> On 11/08/2015 01:53 PM, Bernd Eckenfels wrote:
>>>
 Phil:

> I am not happy about proceeding, though, in the presence of the
>
 -1

> votes.  We like to make decisions by consensus and while this is a
> procedural decision and therefore subject to majority approval, I
> would like to ask those who case negative votes to reconsider.
>
 I have an counter proposal: how about addressing most of the concerns
 first:

 - merge the mavenisation cleanly, it is not asked too much to display
it in master not gh-pages
 - add some samples to the readme
 - adopt commons codestyle

 If those 3 things are done by the submitters I personally would be very
 reliefed (I still would not see a case to use it myself, but at least
 we wont have any ground for the rockstar argument anymore). I am not
 sure about the "incubator" argument, as I understood it, it is not
 needed for IP clearance.

 And given the vote already passed you can just make the above clean-up
 in git(hub) and get it merged to the sandbox.

 gruss
 Bernd

 -
 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
>>
>>
>



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

Re: [VOTE] Release NET 3.4 based on RC2 - resend with corrected tag

2015-11-22 Thread Gary Gregory 
+1

>From src zip: builds OK, reports OK, ASC, MD5, SHA1 OK.

Tested with Java 8 and 7:

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T08:41:47-08:00)
Maven home: E:\Java\apache-maven-3.3.9\bin\..
Java version: 1.8.0_65, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_65\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T08:41:47-08:00)
Maven home: E:\Java\apache-maven-3.3.9\bin\..
Java version: 1.7.0_79, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_79\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

Gary

On Sun, Nov 22, 2015 at 7:58 AM, sebb  wrote:

> It's probably about time to release NET.
> There have been quite a few improvements and fixes since the last version.
>
> [This is a repeat of the original mail, but using a tag that actually
> exists this time]
>
> ==
>
> Net 3.4 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/net/ (svn revision
> 11241)
>
>
> ./binaries/commons-net-3.4-bin.tar.gz.sha1:88411522395b4000b038a94ab007be89ebda2ec3
>
> ./binaries/commons-net-3.4-bin.zip.sha1:f252a45b1610346116c9dd966fec9a15171223d1
>
> ./source/commons-net-3.4-src.tar.gz.sha1:abfba84427a06341e113d59d8f75855e67093087
>
> ./source/commons-net-3.4-src.zip.sha1:f3b38dfcccd8fcdc9ac500a5f8580a19817b
>
>   Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1120/commons-net/commons-net/3.4/
>
> These are the artifacts and their hashes
>
> /commons-net/commons-net/3.4/commons-net-3.4-test-sources.jar
> (SHA1: fdb74119054a2aacc134c56137660d7a0a40e4a8)
> /commons-net/commons-net/3.4/commons-net-3.4-javadoc.jar
> (SHA1: b882750c8dbd480e2b9afd357dcf71d962f2fa03)
> /commons-net/commons-net/3.4/commons-net-3.4-ftp.jar
> (SHA1: 6fc585e5f3dc8333b20110af22a8bae59f5246cb)
> /commons-net/commons-net/3.4/commons-net-3.4-tests.jar
> (SHA1: ce44ebc0e7be56c3bd650700be93c5b377b47573)
> /commons-net/commons-net/3.4/commons-net-3.4.pom
> (SHA1: d1790447a41c848af8cba0919fae7a577fbc744a)
> /commons-net/commons-net/3.4/commons-net-3.4.jar
> (SHA1: 5e984db9554728564d58e90da5d90eff8ae8cf2d)
> /commons-net/commons-net/3.4/commons-net-3.4-sources.jar
> (SHA1: 08439b8f20d7bdec502423732798a639501732c8)
> /commons-net/commons-net/3.4/commons-net-3.4-examples.jar
> (SHA1: 33abb13d790501fc9e4e77a40425bc381d39b9ca)
>
>   Details of changes since 3.3 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/net/RELEASE-NOTES.txt
> http://people.apache.org/~sebb/net-3.4-RC2/changes-report.html
>
>   I have tested this with JDK 1.6, 1.7, 1.8 using maven3.
>
>   The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_4_RC2/
> (svn 1715635)
>
>   N.B. the SVN revision is required because SVN tags are not immutable.
>
>   Site:
> http://people.apache.org/~sebb/net-3.4-RC2/
>   (note some *relative* links are broken and the 3.4 directories are
>   not yet created - these will be OK once the site is deployed)
>
>   download_net.cgi does not work, but the template can be checked at
> http://people.apache.org/~sebb/net-3.4-RC2/download_net.html
>
>   Clirr Report (compared to 3.3):
> http://people.apache.org/~sebb/net-3.4-RC2/clirr-report.html
>
>   Note that adding methods to an interface is binary-compatible, but
> not source-compatible
>   This change is documented in the Release Notes
>
>   RAT Report:
> http://people.apache.org/~sebb/net-3.4-RC2/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. after
> 14:00 GMT 22-Nov 2015
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
>   Thanks!
>
>   Sebb
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-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