Re: [4/7] [text] Updated RELEASE-NOTES.txt in preparation for 1.0 release
> On Mar 6, 2017, at 1:45 PM, sebb wrote: > >> On 6 March 2017 at 18:20, Rob Tompkins wrote: >> >> On Mar 6, 2017, at 11:54 AM, sebb wrote: On 5 March 2017 at 04:05, wrote: Updated RELEASE-NOTES.txt in preparation for 1.0 release Project: http://git-wip-us.apache.org/repos/asf/commons-text/repo Commit: http://git-wip-us.apache.org/repos/asf/commons-text/commit/bfdd0aa8 Tree: http://git-wip-us.apache.org/repos/asf/commons-text/tree/bfdd0aa8 Diff: http://git-wip-us.apache.org/repos/asf/commons-text/diff/bfdd0aa8 Branch: refs/heads/release Commit: bfdd0aa8f794cfcecfd07aa9e506412ba914375a Parents: 85a247b Author: Rob Tompkins Authored: Sat Mar 4 22:54:52 2017 -0500 Committer: Rob Tompkins Committed: Sat Mar 4 22:54:52 2017 -0500 -- RELEASE-NOTES.txt | 42 +++--- 1 file changed, 39 insertions(+), 3 deletions(-) -- http://git-wip-us.apache.org/repos/asf/commons-text/blob/bfdd0aa8/RELEASE-NOTES.txt -- diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt index 56769a8..5964146 100644 --- a/RELEASE-NOTES.txt +++ b/RELEASE-NOTES.txt @@ -1,5 +1,5 @@ Apache Commons Text - Version 1.0-beta-1 + Version 1.0 Release Notes @@ -13,6 +13,42 @@ Java environment. Apache Commons Text is a library focused on algorithms working on strings. + +INCOMPATIBLE CHANGES + + +All package names changed from org.apache.commons.text.beta in 1.0-beta-1 to +org.apache.commons.text in 1.0. + +Methods StringEscapeUtils#escapeHtml3Once and StringEscapeUtils#escapeHtml4Once +have been removed; see TEXT-40 + +JAVA 9 SUPPORT +== + +At our time of release of 1.0-beta-1, our build succeeds with Java 9-ea build 158, >>> >>> That should be 1.0 >> >> Thanks for that catch. You think I should re-build the release candidate? >> Feels like it. > > I don't have a view on that. Mistakes happen. It can be mentioned in > the Announce and fixed on the download site. > > In any case, I would wait in case other issues are found. Sounds good thanks again. > >> -Rob >> >>> +and we believe all of our features to be Java 9 compatible. However, when we run +"mvn clean site" we have failures. + +FIXED BUGS +== + +o TEXT-64: Investigate locale issue in ExtendedMessageFormatTest. Thanks to + chtompki. +o TEXT-69: Resolve PMD/CMD Violations +o TEXT-65: Fixing the 200 checkstyle errors present in 1.0-beta-1. +o TEXT-63: Mutable fields should be private. + +REMOVED +=== + +o TEXT-40: Escape HTML characters only once: revert. + + + +Release Notes for version 1.0-beta-1 + + A NOTE ON THE HISTORY OF THE CODE = @@ -28,8 +64,8 @@ Lang into Commons Text. JAVA 9 SUPPORT == -At our time of release our build succeeds with Java 9-ea build 153, and we -believe all of our features to be Java 9 compatible. +At our time of release of 1.0-beta-1, our build succeeds with Java 9-ea build 153, +and we believe all of our features to be Java 9 compatible. NEW FEATURES >>> >>> - >>> 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: [4/7] [text] Updated RELEASE-NOTES.txt in preparation for 1.0 release
On 6 March 2017 at 18:20, Rob Tompkins wrote: > > >> On Mar 6, 2017, at 11:54 AM, sebb wrote: >> >>> On 5 March 2017 at 04:05, wrote: >>> Updated RELEASE-NOTES.txt in preparation for 1.0 release >>> >>> >>> Project: http://git-wip-us.apache.org/repos/asf/commons-text/repo >>> Commit: http://git-wip-us.apache.org/repos/asf/commons-text/commit/bfdd0aa8 >>> Tree: http://git-wip-us.apache.org/repos/asf/commons-text/tree/bfdd0aa8 >>> Diff: http://git-wip-us.apache.org/repos/asf/commons-text/diff/bfdd0aa8 >>> >>> Branch: refs/heads/release >>> Commit: bfdd0aa8f794cfcecfd07aa9e506412ba914375a >>> Parents: 85a247b >>> Author: Rob Tompkins >>> Authored: Sat Mar 4 22:54:52 2017 -0500 >>> Committer: Rob Tompkins >>> Committed: Sat Mar 4 22:54:52 2017 -0500 >>> >>> -- >>> RELEASE-NOTES.txt | 42 +++--- >>> 1 file changed, 39 insertions(+), 3 deletions(-) >>> -- >>> >>> >>> http://git-wip-us.apache.org/repos/asf/commons-text/blob/bfdd0aa8/RELEASE-NOTES.txt >>> -- >>> diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt >>> index 56769a8..5964146 100644 >>> --- a/RELEASE-NOTES.txt >>> +++ b/RELEASE-NOTES.txt >>> @@ -1,5 +1,5 @@ >>> Apache Commons Text >>> - Version 1.0-beta-1 >>> + Version 1.0 >>> Release Notes >>> >>> >>> @@ -13,6 +13,42 @@ Java environment. >>> >>> Apache Commons Text is a library focused on algorithms working on strings. >>> >>> + >>> +INCOMPATIBLE CHANGES >>> + >>> + >>> +All package names changed from org.apache.commons.text.beta in 1.0-beta-1 >>> to >>> +org.apache.commons.text in 1.0. >>> + >>> +Methods StringEscapeUtils#escapeHtml3Once and >>> StringEscapeUtils#escapeHtml4Once >>> +have been removed; see TEXT-40 >>> + >>> +JAVA 9 SUPPORT >>> +== >>> + >>> +At our time of release of 1.0-beta-1, our build succeeds with Java 9-ea >>> build 158, >> >> That should be 1.0 > > Thanks for that catch. You think I should re-build the release candidate? > Feels like it. I don't have a view on that. Mistakes happen. It can be mentioned in the Announce and fixed on the download site. In any case, I would wait in case other issues are found. > -Rob > >> >>> +and we believe all of our features to be Java 9 compatible. However, when >>> we run >>> +"mvn clean site" we have failures. >>> + >>> +FIXED BUGS >>> +== >>> + >>> +o TEXT-64: Investigate locale issue in ExtendedMessageFormatTest. Thanks >>> to >>> + chtompki. >>> +o TEXT-69: Resolve PMD/CMD Violations >>> +o TEXT-65: Fixing the 200 checkstyle errors present in 1.0-beta-1. >>> +o TEXT-63: Mutable fields should be private. >>> + >>> +REMOVED >>> +=== >>> + >>> +o TEXT-40: Escape HTML characters only once: revert. >>> + >>> + >>> + >>> +Release Notes for version 1.0-beta-1 >>> + >>> + >>> A NOTE ON THE HISTORY OF THE CODE >>> = >>> >>> @@ -28,8 +64,8 @@ Lang into Commons Text. >>> JAVA 9 SUPPORT >>> == >>> >>> -At our time of release our build succeeds with Java 9-ea build 153, and we >>> -believe all of our features to be Java 9 compatible. >>> +At our time of release of 1.0-beta-1, our build succeeds with Java 9-ea >>> build 153, >>> +and we believe all of our features to be Java 9 compatible. >>> >>> NEW FEATURES >>> >>> >> >> - >> 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: [4/7] [text] Updated RELEASE-NOTES.txt in preparation for 1.0 release
> On Mar 6, 2017, at 11:54 AM, sebb wrote: > >> On 5 March 2017 at 04:05, wrote: >> Updated RELEASE-NOTES.txt in preparation for 1.0 release >> >> >> Project: http://git-wip-us.apache.org/repos/asf/commons-text/repo >> Commit: http://git-wip-us.apache.org/repos/asf/commons-text/commit/bfdd0aa8 >> Tree: http://git-wip-us.apache.org/repos/asf/commons-text/tree/bfdd0aa8 >> Diff: http://git-wip-us.apache.org/repos/asf/commons-text/diff/bfdd0aa8 >> >> Branch: refs/heads/release >> Commit: bfdd0aa8f794cfcecfd07aa9e506412ba914375a >> Parents: 85a247b >> Author: Rob Tompkins >> Authored: Sat Mar 4 22:54:52 2017 -0500 >> Committer: Rob Tompkins >> Committed: Sat Mar 4 22:54:52 2017 -0500 >> >> -- >> RELEASE-NOTES.txt | 42 +++--- >> 1 file changed, 39 insertions(+), 3 deletions(-) >> -- >> >> >> http://git-wip-us.apache.org/repos/asf/commons-text/blob/bfdd0aa8/RELEASE-NOTES.txt >> -- >> diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt >> index 56769a8..5964146 100644 >> --- a/RELEASE-NOTES.txt >> +++ b/RELEASE-NOTES.txt >> @@ -1,5 +1,5 @@ >> Apache Commons Text >> - Version 1.0-beta-1 >> + Version 1.0 >> Release Notes >> >> >> @@ -13,6 +13,42 @@ Java environment. >> >> Apache Commons Text is a library focused on algorithms working on strings. >> >> + >> +INCOMPATIBLE CHANGES >> + >> + >> +All package names changed from org.apache.commons.text.beta in 1.0-beta-1 to >> +org.apache.commons.text in 1.0. >> + >> +Methods StringEscapeUtils#escapeHtml3Once and >> StringEscapeUtils#escapeHtml4Once >> +have been removed; see TEXT-40 >> + >> +JAVA 9 SUPPORT >> +== >> + >> +At our time of release of 1.0-beta-1, our build succeeds with Java 9-ea >> build 158, > > That should be 1.0 Thanks for that catch. You think I should re-build the release candidate? Feels like it. -Rob > >> +and we believe all of our features to be Java 9 compatible. However, when >> we run >> +"mvn clean site" we have failures. >> + >> +FIXED BUGS >> +== >> + >> +o TEXT-64: Investigate locale issue in ExtendedMessageFormatTest. Thanks >> to >> + chtompki. >> +o TEXT-69: Resolve PMD/CMD Violations >> +o TEXT-65: Fixing the 200 checkstyle errors present in 1.0-beta-1. >> +o TEXT-63: Mutable fields should be private. >> + >> +REMOVED >> +=== >> + >> +o TEXT-40: Escape HTML characters only once: revert. >> + >> + >> + >> +Release Notes for version 1.0-beta-1 >> + >> + >> A NOTE ON THE HISTORY OF THE CODE >> = >> >> @@ -28,8 +64,8 @@ Lang into Commons Text. >> JAVA 9 SUPPORT >> == >> >> -At our time of release our build succeeds with Java 9-ea build 153, and we >> -believe all of our features to be Java 9 compatible. >> +At our time of release of 1.0-beta-1, our build succeeds with Java 9-ea >> build 153, >> +and we believe all of our features to be Java 9 compatible. >> >> NEW FEATURES >> >> > > - > 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: [4/7] [text] Updated RELEASE-NOTES.txt in preparation for 1.0 release
On 5 March 2017 at 04:05, wrote: > Updated RELEASE-NOTES.txt in preparation for 1.0 release > > > Project: http://git-wip-us.apache.org/repos/asf/commons-text/repo > Commit: http://git-wip-us.apache.org/repos/asf/commons-text/commit/bfdd0aa8 > Tree: http://git-wip-us.apache.org/repos/asf/commons-text/tree/bfdd0aa8 > Diff: http://git-wip-us.apache.org/repos/asf/commons-text/diff/bfdd0aa8 > > Branch: refs/heads/release > Commit: bfdd0aa8f794cfcecfd07aa9e506412ba914375a > Parents: 85a247b > Author: Rob Tompkins > Authored: Sat Mar 4 22:54:52 2017 -0500 > Committer: Rob Tompkins > Committed: Sat Mar 4 22:54:52 2017 -0500 > > -- > RELEASE-NOTES.txt | 42 +++--- > 1 file changed, 39 insertions(+), 3 deletions(-) > -- > > > http://git-wip-us.apache.org/repos/asf/commons-text/blob/bfdd0aa8/RELEASE-NOTES.txt > -- > diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt > index 56769a8..5964146 100644 > --- a/RELEASE-NOTES.txt > +++ b/RELEASE-NOTES.txt > @@ -1,5 +1,5 @@ >Apache Commons Text > - Version 1.0-beta-1 > + Version 1.0 > Release Notes > > > @@ -13,6 +13,42 @@ Java environment. > > Apache Commons Text is a library focused on algorithms working on strings. > > + > +INCOMPATIBLE CHANGES > + > + > +All package names changed from org.apache.commons.text.beta in 1.0-beta-1 to > +org.apache.commons.text in 1.0. > + > +Methods StringEscapeUtils#escapeHtml3Once and > StringEscapeUtils#escapeHtml4Once > +have been removed; see TEXT-40 > + > +JAVA 9 SUPPORT > +== > + > +At our time of release of 1.0-beta-1, our build succeeds with Java 9-ea > build 158, That should be 1.0 > +and we believe all of our features to be Java 9 compatible. However, when we > run > +"mvn clean site" we have failures. > + > +FIXED BUGS > +== > + > +o TEXT-64: Investigate locale issue in ExtendedMessageFormatTest. Thanks to > + chtompki. > +o TEXT-69: Resolve PMD/CMD Violations > +o TEXT-65: Fixing the 200 checkstyle errors present in 1.0-beta-1. > +o TEXT-63: Mutable fields should be private. > + > +REMOVED > +=== > + > +o TEXT-40: Escape HTML characters only once: revert. > + > + > + > +Release Notes for version 1.0-beta-1 > + > + > A NOTE ON THE HISTORY OF THE CODE > = > > @@ -28,8 +64,8 @@ Lang into Commons Text. > JAVA 9 SUPPORT > == > > -At our time of release our build succeeds with Java 9-ea build 153, and we > -believe all of our features to be Java 9 compatible. > +At our time of release of 1.0-beta-1, our build succeeds with Java 9-ea > build 153, > +and we believe all of our features to be Java 9 compatible. > > NEW FEATURES > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [POOL][DBCP] Release plans
For Pool, I'm not exactly sure why we need a Java 6 compatible implementation for the next minor version (2.5). We've had the EOL discussion before, and even Java 7 is at that point. The only reason I'd look at updating DBCP to use Java 8 is to support JDBC 4.2 < https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/jdbc_42.html>. I'm not sure if that would require a new major version (3.0) or if we'd just support it in 2.3 or 2.4. On 6 March 2017 at 03:15, Romain Manni-Bucau wrote: > 2017-03-06 10:06 GMT+01:00 Mark Thomas : > > > On 05/03/17 18:21, Matt Sicker wrote: > > > I'm also thinking we might want to upgrade to Java 7 for pool 2.5 as > dbcp > > > 2.x has required it from the beginning. I'm not exactly sure if > anything > > > JDBC changed in Java 8 to warrant an upgrade to Java 8 for dbcp 2.3, > but > > > it's also worth mentioning if needed. > > > > Is there any reason - apart from the age of Java 6 - to make Java 7 the > > minimum for Pool? > > > > Tomcat 8 uses DBCP 2 and Pool 2 and - because it implements parts Java > > EE 7 specification, has to run on Java 7. An upgrade to Java 8 would be > > an annoyance but one the Tomcat project could work around if it had to. > > > > > Same for TomEE* (openejb part too which runs without tomcat) which would > mean for both projects to fork (repackage) pool and dbcp > > > > Mark > > > > > > > > On 5 March 2017 at 11:59, Pascal Schumacher > > > wrote: > > > > > >> Great new. :) > > >> > > >> As far as I remember there were various request for DBCP 2.2 (and we > > would > > >> like to update to pool 2.4.3 at work). > > >> > > >> Thank you very much, > > >> Pascal > > >> > > >> Am 05.03.2017 um 18:30 schrieb Matt Sicker: > > >> > > >>> I've started a lazy vote to migrate Pool to Git. After that, I'd like > > to > > >>> take a whack at starting a release candidate for pool 2.4.3. After > > that, > > >>> we > > >>> can upgrade DBCP to pool 2.4.3 and do a release of DBCP to 2.2. > > >>> > > >>> > > >> > > >> - > > >> 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 > > > > > -- Matt Sicker
[VOTE] Release Commons Text 1.0 based on RC1
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
[VOTE] Release Commons Text 1.0 based on RC1
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: [POOL][DBCP] Release plans
2017-03-06 10:06 GMT+01:00 Mark Thomas : > On 05/03/17 18:21, Matt Sicker wrote: > > I'm also thinking we might want to upgrade to Java 7 for pool 2.5 as dbcp > > 2.x has required it from the beginning. I'm not exactly sure if anything > > JDBC changed in Java 8 to warrant an upgrade to Java 8 for dbcp 2.3, but > > it's also worth mentioning if needed. > > Is there any reason - apart from the age of Java 6 - to make Java 7 the > minimum for Pool? > > Tomcat 8 uses DBCP 2 and Pool 2 and - because it implements parts Java > EE 7 specification, has to run on Java 7. An upgrade to Java 8 would be > an annoyance but one the Tomcat project could work around if it had to. > > Same for TomEE* (openejb part too which runs without tomcat) which would mean for both projects to fork (repackage) pool and dbcp > Mark > > > > > On 5 March 2017 at 11:59, Pascal Schumacher > > wrote: > > > >> Great new. :) > >> > >> As far as I remember there were various request for DBCP 2.2 (and we > would > >> like to update to pool 2.4.3 at work). > >> > >> Thank you very much, > >> Pascal > >> > >> Am 05.03.2017 um 18:30 schrieb Matt Sicker: > >> > >>> I've started a lazy vote to migrate Pool to Git. After that, I'd like > to > >>> take a whack at starting a release candidate for pool 2.4.3. After > that, > >>> we > >>> can upgrade DBCP to pool 2.4.3 and do a release of DBCP to 2.2. > >>> > >>> > >> > >> - > >> 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: [POOL][DBCP] Release plans
On 05/03/17 18:21, Matt Sicker wrote: > I'm also thinking we might want to upgrade to Java 7 for pool 2.5 as dbcp > 2.x has required it from the beginning. I'm not exactly sure if anything > JDBC changed in Java 8 to warrant an upgrade to Java 8 for dbcp 2.3, but > it's also worth mentioning if needed. Is there any reason - apart from the age of Java 6 - to make Java 7 the minimum for Pool? Tomcat 8 uses DBCP 2 and Pool 2 and - because it implements parts Java EE 7 specification, has to run on Java 7. An upgrade to Java 8 would be an annoyance but one the Tomcat project could work around if it had to. Mark > > On 5 March 2017 at 11:59, Pascal Schumacher > wrote: > >> Great new. :) >> >> As far as I remember there were various request for DBCP 2.2 (and we would >> like to update to pool 2.4.3 at work). >> >> Thank you very much, >> Pascal >> >> Am 05.03.2017 um 18:30 schrieb Matt Sicker: >> >>> I've started a lazy vote to migrate Pool to Git. After that, I'd like to >>> take a whack at starting a release candidate for pool 2.4.3. After that, >>> we >>> can upgrade DBCP to pool 2.4.3 and do a release of DBCP to 2.2. >>> >>> >> >> - >> 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
