Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-24 Thread Romain Manni-Bucau 
Ok, will try this week-end. Thanks for the feedback.

Romain Manni-Bucau
@rmannibucau |  Blog | Old Blog | Github | LinkedIn


2017-10-25 6:42 GMT+02:00 Gary Gregory :
> IMO, you should redo the tag and rewrite the VOTE email following the
> template in http://commons.apache.org/releases/prepare.html
>
> Gary
>
> On Tue, Oct 24, 2017 at 10:40 PM, Romain Manni-Bucau 
> wrote:
>
>> Hmm,
>>
>> Read that page but the answer is probably hidden in the commons parent - rc
>> property? - cause it is not written how a rc version ends in a not rc
>> version for binaries on nexus with the release plugin. Will check which
>> magic we do here later this week but anyway shouldnt block the release IMO
>> since already done, no?
>>
>> Le 25 oct. 2017 06:00, "Gary Gregory"  a écrit :
>>
>> > On Tue, Oct 24, 2017 at 9:28 PM, kenneth mcfarland <
>> > kennethpmcfarl...@gmail.com> wrote:
>> >
>> > > Gary, I can't help but say great work on all of these releases. #praise
>> > >
>> >
>> > Thank you Kenneth.
>> >
>> > Gary
>> >
>> >
>> > >
>> > > On Oct 24, 2017 8:24 PM, "Gary Gregory" 
>> wrote:
>> > >
>> > > > Our process documented here http://commons.apache.org/
>> > > > releases/prepare.html
>> > > > makes it pretty clear that the RC tag should be labeled as such and
>> > that
>> > > a
>> > > > tag like "commons-jcs-2.2.1" should only be created after a VOTE
>> > passes.
>> > > >
>> > > > Gary
>> > > >
>> > > > On Sun, Oct 22, 2017 at 3:17 PM, Romain Manni-Bucau <
>> > > rmannibu...@gmail.com
>> > > > >
>> > > > wrote:
>> > > >
>> > > > > So i just copy the mvn release tag? Sounds quite useless since the
>> > tag
>> > > is
>> > > > > done no?
>> > > > >
>> > > > > Le 22 oct. 2017 21:14, "Gary Gregory"  a
>> > > écrit :
>> > > > >
>> > > > > > We need a tag for an RC in order to match a VOTE thread with the
>> > code
>> > > > > being
>> > > > > > proposed.
>> > > > > >
>> > > > > > Gary
>> > > > > >
>> > > > > > On Oct 22, 2017 10:24, "Romain Manni-Bucau" <
>> rmannibu...@gmail.com
>> > >
>> > > > > wrote:
>> > > > > >
>> > > > > > > Revision is r1812876.
>> > > > > > >
>> > > > > > > Have to admit im not sure about the hack to use to have a rc
>> tag
>> > > > (name)
>> > > > > > > without rc artifacts which wouldnt match the target release
>> with
>> > > mvn
>> > > > > > > release plugin but dont think it is a blocker (but still happy
>> to
>> > > > learn
>> > > > > > it
>> > > > > > > ;)).
>> > > > > > >
>> > > > > > > Le 22 oct. 2017 17:29, "Gary Gregory" 
>> a
>> > > > > écrit :
>> > > > > > >
>> > > > > > > The tag name is wrong because it is not postfixed with RC2. All
>> > SVN
>> > > > > links
>> > > > > > > should be accompanied with a revision number.
>> > > > > > >
>> > > > > > > Gary
>> > > > > > >
>> > > > > > > On Oct 22, 2017 02:31, "Romain Manni-Bucau" <
>> > rmannibu...@gmail.com
>> > > >
>> > > > > > wrote:
>> > > > > > >
>> > > > > > > Hello guys,
>> > > > > > >
>> > > > > > > I would like to release the [jcs] component to resolve a cdi
>> > > > > > > performance issue (JCS-183) and a bug in dispose method when
>> log
>> > > are
>> > > > > > > in debug level (JCS-184).
>> > > > > > >
>> > > > > > >  Maven artifacts are at:
>> > > > > > > https://repository.apache.org/service/local/repositories/
>> > > > > > > orgapachecommons-1281/
>> > > > > > >
>> > > > > > >  The Subversion tag is:
>> > > > > > > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/
>> > > > > > commons-jcs-2.2.1/
>> > > > > > >
>> > > > > > >  The release notes are available at:
>> > > > > > > https://issues.apache.org/jira/projects/JCS/versions/12341663
>> > > > > > > https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE-
>> > > NOTES.txt
>> > > > > > >
>> > > > > > >  The staged sources and binaries are available at
>> > > > > > > https://dist.apache.org/repos/dist/dev/commons/jcs/
>> > > > > > >
>> > > > > > >  Please review the release candidate and vote.
>> > > > > > >
>> > > > > > >[ ] +1 Release these artifacts
>> > > > > > >[ ] +-0 don't care
>> > > > > > >[ ] -1 I oppose this release because ${reason}
>> > > > > > >
>> > > > > > > Romain Manni-Bucau
>> > > > > > > @rmannibucau |  Blog | Old Blog | Github | LinkedIn
>> > > > > > >
>> > > > > > > 
>> > > > -
>> > > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> > > > > > > For additional commands, e-mail: dev-h...@commons.apache.org
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>

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

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-24 Thread Gary Gregory 
IMO, you should redo the tag and rewrite the VOTE email following the
template in http://commons.apache.org/releases/prepare.html

Gary

On Tue, Oct 24, 2017 at 10:40 PM, Romain Manni-Bucau 
wrote:

> Hmm,
>
> Read that page but the answer is probably hidden in the commons parent - rc
> property? - cause it is not written how a rc version ends in a not rc
> version for binaries on nexus with the release plugin. Will check which
> magic we do here later this week but anyway shouldnt block the release IMO
> since already done, no?
>
> Le 25 oct. 2017 06:00, "Gary Gregory"  a écrit :
>
> > On Tue, Oct 24, 2017 at 9:28 PM, kenneth mcfarland <
> > kennethpmcfarl...@gmail.com> wrote:
> >
> > > Gary, I can't help but say great work on all of these releases. #praise
> > >
> >
> > Thank you Kenneth.
> >
> > Gary
> >
> >
> > >
> > > On Oct 24, 2017 8:24 PM, "Gary Gregory" 
> wrote:
> > >
> > > > Our process documented here http://commons.apache.org/
> > > > releases/prepare.html
> > > > makes it pretty clear that the RC tag should be labeled as such and
> > that
> > > a
> > > > tag like "commons-jcs-2.2.1" should only be created after a VOTE
> > passes.
> > > >
> > > > Gary
> > > >
> > > > On Sun, Oct 22, 2017 at 3:17 PM, Romain Manni-Bucau <
> > > rmannibu...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > So i just copy the mvn release tag? Sounds quite useless since the
> > tag
> > > is
> > > > > done no?
> > > > >
> > > > > Le 22 oct. 2017 21:14, "Gary Gregory"  a
> > > écrit :
> > > > >
> > > > > > We need a tag for an RC in order to match a VOTE thread with the
> > code
> > > > > being
> > > > > > proposed.
> > > > > >
> > > > > > Gary
> > > > > >
> > > > > > On Oct 22, 2017 10:24, "Romain Manni-Bucau" <
> rmannibu...@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Revision is r1812876.
> > > > > > >
> > > > > > > Have to admit im not sure about the hack to use to have a rc
> tag
> > > > (name)
> > > > > > > without rc artifacts which wouldnt match the target release
> with
> > > mvn
> > > > > > > release plugin but dont think it is a blocker (but still happy
> to
> > > > learn
> > > > > > it
> > > > > > > ;)).
> > > > > > >
> > > > > > > Le 22 oct. 2017 17:29, "Gary Gregory" 
> a
> > > > > écrit :
> > > > > > >
> > > > > > > The tag name is wrong because it is not postfixed with RC2. All
> > SVN
> > > > > links
> > > > > > > should be accompanied with a revision number.
> > > > > > >
> > > > > > > Gary
> > > > > > >
> > > > > > > On Oct 22, 2017 02:31, "Romain Manni-Bucau" <
> > rmannibu...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > Hello guys,
> > > > > > >
> > > > > > > I would like to release the [jcs] component to resolve a cdi
> > > > > > > performance issue (JCS-183) and a bug in dispose method when
> log
> > > are
> > > > > > > in debug level (JCS-184).
> > > > > > >
> > > > > > >  Maven artifacts are at:
> > > > > > > https://repository.apache.org/service/local/repositories/
> > > > > > > orgapachecommons-1281/
> > > > > > >
> > > > > > >  The Subversion tag is:
> > > > > > > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> > > > > > commons-jcs-2.2.1/
> > > > > > >
> > > > > > >  The release notes are available at:
> > > > > > > https://issues.apache.org/jira/projects/JCS/versions/12341663
> > > > > > > https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE-
> > > NOTES.txt
> > > > > > >
> > > > > > >  The staged sources and binaries are available at
> > > > > > > https://dist.apache.org/repos/dist/dev/commons/jcs/
> > > > > > >
> > > > > > >  Please review the release candidate and vote.
> > > > > > >
> > > > > > >[ ] +1 Release these artifacts
> > > > > > >[ ] +-0 don't care
> > > > > > >[ ] -1 I oppose this release because ${reason}
> > > > > > >
> > > > > > > Romain Manni-Bucau
> > > > > > > @rmannibucau |  Blog | Old Blog | Github | LinkedIn
> > > > > > >
> > > > > > > 
> > > > -
> > > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > > > > > For additional commands, e-mail: dev-h...@commons.apache.org
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-24 Thread Romain Manni-Bucau 
Hmm,

Read that page but the answer is probably hidden in the commons parent - rc
property? - cause it is not written how a rc version ends in a not rc
version for binaries on nexus with the release plugin. Will check which
magic we do here later this week but anyway shouldnt block the release IMO
since already done, no?

Le 25 oct. 2017 06:00, "Gary Gregory"  a écrit :

> On Tue, Oct 24, 2017 at 9:28 PM, kenneth mcfarland <
> kennethpmcfarl...@gmail.com> wrote:
>
> > Gary, I can't help but say great work on all of these releases. #praise
> >
>
> Thank you Kenneth.
>
> Gary
>
>
> >
> > On Oct 24, 2017 8:24 PM, "Gary Gregory"  wrote:
> >
> > > Our process documented here http://commons.apache.org/
> > > releases/prepare.html
> > > makes it pretty clear that the RC tag should be labeled as such and
> that
> > a
> > > tag like "commons-jcs-2.2.1" should only be created after a VOTE
> passes.
> > >
> > > Gary
> > >
> > > On Sun, Oct 22, 2017 at 3:17 PM, Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > > >
> > > wrote:
> > >
> > > > So i just copy the mvn release tag? Sounds quite useless since the
> tag
> > is
> > > > done no?
> > > >
> > > > Le 22 oct. 2017 21:14, "Gary Gregory"  a
> > écrit :
> > > >
> > > > > We need a tag for an RC in order to match a VOTE thread with the
> code
> > > > being
> > > > > proposed.
> > > > >
> > > > > Gary
> > > > >
> > > > > On Oct 22, 2017 10:24, "Romain Manni-Bucau"  >
> > > > wrote:
> > > > >
> > > > > > Revision is r1812876.
> > > > > >
> > > > > > Have to admit im not sure about the hack to use to have a rc tag
> > > (name)
> > > > > > without rc artifacts which wouldnt match the target release with
> > mvn
> > > > > > release plugin but dont think it is a blocker (but still happy to
> > > learn
> > > > > it
> > > > > > ;)).
> > > > > >
> > > > > > Le 22 oct. 2017 17:29, "Gary Gregory"  a
> > > > écrit :
> > > > > >
> > > > > > The tag name is wrong because it is not postfixed with RC2. All
> SVN
> > > > links
> > > > > > should be accompanied with a revision number.
> > > > > >
> > > > > > Gary
> > > > > >
> > > > > > On Oct 22, 2017 02:31, "Romain Manni-Bucau" <
> rmannibu...@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > Hello guys,
> > > > > >
> > > > > > I would like to release the [jcs] component to resolve a cdi
> > > > > > performance issue (JCS-183) and a bug in dispose method when log
> > are
> > > > > > in debug level (JCS-184).
> > > > > >
> > > > > >  Maven artifacts are at:
> > > > > > https://repository.apache.org/service/local/repositories/
> > > > > > orgapachecommons-1281/
> > > > > >
> > > > > >  The Subversion tag is:
> > > > > > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> > > > > commons-jcs-2.2.1/
> > > > > >
> > > > > >  The release notes are available at:
> > > > > > https://issues.apache.org/jira/projects/JCS/versions/12341663
> > > > > > https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE-
> > NOTES.txt
> > > > > >
> > > > > >  The staged sources and binaries are available at
> > > > > > https://dist.apache.org/repos/dist/dev/commons/jcs/
> > > > > >
> > > > > >  Please review the release candidate and vote.
> > > > > >
> > > > > >[ ] +1 Release these artifacts
> > > > > >[ ] +-0 don't care
> > > > > >[ ] -1 I oppose this release because ${reason}
> > > > > >
> > > > > > Romain Manni-Bucau
> > > > > > @rmannibucau |  Blog | Old Blog | Github | LinkedIn
> > > > > >
> > > > > > 
> > > -
> > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > > > > For additional commands, e-mail: dev-h...@commons.apache.org
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [RDF] Commons release?

2017-10-24 Thread Gary Gregory 
Maybe what is in master is enough?

Gary

On Tue, Oct 24, 2017 at 10:31 PM, Bruno P. Kinoshita <
brunodepau...@yahoo.com.br.invalid> wrote:

> Not so familiar, more familiar with Jena, but they are related.
> If nobody else volunteers, I can try to spend a weekend triaging issues
> and seeing if I can catch up with the changes since the last release and
> volunteer to cut a new release.
> CheersBruno
>
>   From: Gary Gregory 
>  To: Commons Developers List 
>  Sent: Wednesday, 25 October 2017 4:25 PM
>  Subject: Re: [RDF] Commons release?
>
> Hopefully someone who is familiar with Commons RDF is reading this...
>
> Gary
>
> On Fri, Oct 20, 2017 at 2:25 PM, Aaron Coburn  wrote:
>
> > Hello,
> >
> > I wanted to check in on the status of a 0.4.0 release of Commons RDF. It
> > seems that all of the open PRs have been merged. Any idea on a timeframe
> > for the next release?
> >
> > Thanks,
> > Aaron
> >
> > On 9/19/17, 5:58 PM, "Aaron Coburn"  wrote:
> >
> >Sergio,
> >
> >Thanks! The LDP server implementation is spread across quite a few
> > repositories in this github organization: https://github.com/trellis-ldp
> > (everything is Apache2 licensed), but the core abstractions are found in:
> >
> >API: https://github.com/trellis-ldp/trellis-api
> >SPI: https://github.com/trellis-ldp/trellis-spi
> >HTTP layer: https://github.com/trellis-ldp/trellis-http
> >
> >Most of the components have already been released to maven central,
> > but I'm still working on a few of them (particularly the HTTP layer and
> the
> > persistence layer).
> >
> >The main difference between this and, say, Marmotta, is that this
> > implementation is designed to scale horizontally. And by making use of
> > Commons-RDF, the interfaces of this LDP server aren't tied to a
> particular
> > RDF library implementation -- e.g. Jena or RDF4J -- though I do use Jena
> in
> > the implementation code. I am also making significant use of ZooKeeper
> > (Curator), Kafka and Beam.
> >
> >Aaron
> >
> >> On Sep 19, 2017, at 5:27 PM, Sergio Fernández 
> > wrote:
> >>
> >> Hi Aaron,
> >>
> >> you're right, we have quite some things to release. But first I' d
> > like to
> >> take a look to our backlog, because we have some open PRs. Hopefully
> > I'll
> >> have some time later this week, at the latest on the weekend.
> >>
> >> Just for curiosity, can you provide us a pointer to your Commons
> > RDF-based
> >> LDP implementation?
> >>
> >> Thanks.
> >>
> >> Cheers,
> >>
> >>
> >>
> >> On Mon, Sep 18, 2017 at 2:24 PM, Aaron Coburn 
> > wrote:
> >>
> >>> Hi!
> >>>
> >>> The last release of commons-rdf was from last November, and there
> > are some
> >>> nice features in the master branch that I would really like to use
> > --
> >>> especially the improved OSGi support. It seems that there are a few
> >>> unresolved jira issues, such that this wouldn't be a 1.0 release,
> > but even
> >>> a 0.4.0 release would be great.
> >>>
> >>> As a little background, over the last several months I've built a
> > server
> >>> implementation of the W3C Linked Data Platform in which commons-rdf
> >>> provides all of the core RDF abstractions.
> >>>
> >>> Would it be possible to move forward with a release? I would be
> > more than
> >>> happy to help out.
> >>>
> >>> Thanks,
> >>> Aaron
> >>>
> >>> acob...@apache.org
> >>> 
> > -
> >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >>> For additional commands, e-mail: dev-h...@commons.apache.org
> >>>
> >>>
> >
> >?B�
> > CB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��[[ۜ˘\?
> > X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��[[ۜ˘\?X�?K�ܙ�B
> >
> >
> >
>
>

Re: [RDF] Commons release?

2017-10-24 Thread Bruno P. Kinoshita 
Not so familiar, more familiar with Jena, but they are related.
If nobody else volunteers, I can try to spend a weekend triaging issues and 
seeing if I can catch up with the changes since the last release and volunteer 
to cut a new release.
CheersBruno

  From: Gary Gregory 
 To: Commons Developers List  
 Sent: Wednesday, 25 October 2017 4:25 PM
 Subject: Re: [RDF] Commons release?
   
Hopefully someone who is familiar with Commons RDF is reading this...

Gary

On Fri, Oct 20, 2017 at 2:25 PM, Aaron Coburn  wrote:

> Hello,
>
> I wanted to check in on the status of a 0.4.0 release of Commons RDF. It
> seems that all of the open PRs have been merged. Any idea on a timeframe
> for the next release?
>
> Thanks,
> Aaron
>
> On 9/19/17, 5:58 PM, "Aaron Coburn"  wrote:
>
>    Sergio,
>
>    Thanks! The LDP server implementation is spread across quite a few
> repositories in this github organization: https://github.com/trellis-ldp
> (everything is Apache2 licensed), but the core abstractions are found in:
>
>    API: https://github.com/trellis-ldp/trellis-api
>    SPI: https://github.com/trellis-ldp/trellis-spi
>    HTTP layer: https://github.com/trellis-ldp/trellis-http
>
>    Most of the components have already been released to maven central,
> but I'm still working on a few of them (particularly the HTTP layer and the
> persistence layer).
>
>    The main difference between this and, say, Marmotta, is that this
> implementation is designed to scale horizontally. And by making use of
> Commons-RDF, the interfaces of this LDP server aren't tied to a particular
> RDF library implementation -- e.g. Jena or RDF4J -- though I do use Jena in
> the implementation code. I am also making significant use of ZooKeeper
> (Curator), Kafka and Beam.
>
>    Aaron
>
>    > On Sep 19, 2017, at 5:27 PM, Sergio Fernández 
> wrote:
>    >
>    > Hi Aaron,
>    >
>    > you're right, we have quite some things to release. But first I' d
> like to
>    > take a look to our backlog, because we have some open PRs. Hopefully
> I'll
>    > have some time later this week, at the latest on the weekend.
>    >
>    > Just for curiosity, can you provide us a pointer to your Commons
> RDF-based
>    > LDP implementation?
>    >
>    > Thanks.
>    >
>    > Cheers,
>    >
>    >
>    >
>    > On Mon, Sep 18, 2017 at 2:24 PM, Aaron Coburn 
> wrote:
>    >
>    >> Hi!
>    >>
>    >> The last release of commons-rdf was from last November, and there
> are some
>    >> nice features in the master branch that I would really like to use
> --
>    >> especially the improved OSGi support. It seems that there are a few
>    >> unresolved jira issues, such that this wouldn't be a 1.0 release,
> but even
>    >> a 0.4.0 release would be great.
>    >>
>    >> As a little background, over the last several months I've built a
> server
>    >> implementation of the W3C Linked Data Platform in which commons-rdf
>    >> provides all of the core RDF abstractions.
>    >>
>    >> Would it be possible to move forward with a release? I would be
> more than
>    >> happy to help out.
>    >>
>    >> Thanks,
>    >> Aaron
>    >>
>    >> acob...@apache.org
>    >> 
> -
>    >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>    >> For additional commands, e-mail: dev-h...@commons.apache.org
>    >>
>    >>
>
>    ?B�
> CB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��[[ۜ˘\?
> X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��[[ۜ˘\?X�?K�ܙ�B
>
>
>

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-24 Thread Gary Gregory 
On Tue, Oct 24, 2017 at 9:28 PM, kenneth mcfarland <
kennethpmcfarl...@gmail.com> wrote:

> Gary, I can't help but say great work on all of these releases. #praise
>

Thank you Kenneth.

Gary


>
> On Oct 24, 2017 8:24 PM, "Gary Gregory"  wrote:
>
> > Our process documented here http://commons.apache.org/
> > releases/prepare.html
> > makes it pretty clear that the RC tag should be labeled as such and that
> a
> > tag like "commons-jcs-2.2.1" should only be created after a VOTE passes.
> >
> > Gary
> >
> > On Sun, Oct 22, 2017 at 3:17 PM, Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >
> > wrote:
> >
> > > So i just copy the mvn release tag? Sounds quite useless since the tag
> is
> > > done no?
> > >
> > > Le 22 oct. 2017 21:14, "Gary Gregory"  a
> écrit :
> > >
> > > > We need a tag for an RC in order to match a VOTE thread with the code
> > > being
> > > > proposed.
> > > >
> > > > Gary
> > > >
> > > > On Oct 22, 2017 10:24, "Romain Manni-Bucau" 
> > > wrote:
> > > >
> > > > > Revision is r1812876.
> > > > >
> > > > > Have to admit im not sure about the hack to use to have a rc tag
> > (name)
> > > > > without rc artifacts which wouldnt match the target release with
> mvn
> > > > > release plugin but dont think it is a blocker (but still happy to
> > learn
> > > > it
> > > > > ;)).
> > > > >
> > > > > Le 22 oct. 2017 17:29, "Gary Gregory"  a
> > > écrit :
> > > > >
> > > > > The tag name is wrong because it is not postfixed with RC2. All SVN
> > > links
> > > > > should be accompanied with a revision number.
> > > > >
> > > > > Gary
> > > > >
> > > > > On Oct 22, 2017 02:31, "Romain Manni-Bucau"  >
> > > > wrote:
> > > > >
> > > > > Hello guys,
> > > > >
> > > > > I would like to release the [jcs] component to resolve a cdi
> > > > > performance issue (JCS-183) and a bug in dispose method when log
> are
> > > > > in debug level (JCS-184).
> > > > >
> > > > >  Maven artifacts are at:
> > > > > https://repository.apache.org/service/local/repositories/
> > > > > orgapachecommons-1281/
> > > > >
> > > > >  The Subversion tag is:
> > > > > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> > > > commons-jcs-2.2.1/
> > > > >
> > > > >  The release notes are available at:
> > > > > https://issues.apache.org/jira/projects/JCS/versions/12341663
> > > > > https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE-
> NOTES.txt
> > > > >
> > > > >  The staged sources and binaries are available at
> > > > > https://dist.apache.org/repos/dist/dev/commons/jcs/
> > > > >
> > > > >  Please review the release candidate and vote.
> > > > >
> > > > >[ ] +1 Release these artifacts
> > > > >[ ] +-0 don't care
> > > > >[ ] -1 I oppose this release because ${reason}
> > > > >
> > > > > Romain Manni-Bucau
> > > > > @rmannibucau |  Blog | Old Blog | Github | LinkedIn
> > > > >
> > > > > 
> > -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > > > For additional commands, e-mail: dev-h...@commons.apache.org
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-24 Thread Matt Sicker 
On 22 October 2017 at 16:17, Romain Manni-Bucau 
wrote:

> So i just copy the mvn release tag? Sounds quite useless since the tag is
> done no?
>

A release candidate is supposed to match the eventual release at some
point; that's why it's a "candidate". Making a copy of an RC tag to make
the final release tag makes perfect sense in that context.

-- 
Matt Sicker

Re: [LOGGING] Problems updating to lastest commons parent

2017-10-24 Thread Gary Gregory 
Remove the version specifier for build-helper-maven-plugin, this will pick
up the version from the parent POM, which I locally updated from 34 to 42.
Then you'll run into some other error due to how this old build wants to
name jars.

Gary

On Sat, Oct 21, 2017 at 2:30 AM, Benedikt Ritter  wrote:

> Hi,
>
> when I update commons-logging to use Commons parent 42, I get build
> failures:
>
> ~/w/a/c/commons-logging > mvn clean verify
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Commons Logging 1.2.1-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.744 s
> [INFO] Finished at: 2017-10-21T10:30:12+02:00
> [INFO] Final Memory: 12M/245M
> [INFO] 
> 
> [ERROR] Could not find goal 'parse-version' in plugin
> org.codehaus.mojo:build-helper-maven-plugin:1.0 among available goals
> add-source, add-test-source, attach-artifact -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/
> MojoNotFoundException
>
> Any idea how to fix this?
>
> Regards,
> Benedikt
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-24 Thread kenneth mcfarland 
Gary, I can't help but say great work on all of these releases. #praise

On Oct 24, 2017 8:24 PM, "Gary Gregory"  wrote:

> Our process documented here http://commons.apache.org/
> releases/prepare.html
> makes it pretty clear that the RC tag should be labeled as such and that a
> tag like "commons-jcs-2.2.1" should only be created after a VOTE passes.
>
> Gary
>
> On Sun, Oct 22, 2017 at 3:17 PM, Romain Manni-Bucau  >
> wrote:
>
> > So i just copy the mvn release tag? Sounds quite useless since the tag is
> > done no?
> >
> > Le 22 oct. 2017 21:14, "Gary Gregory"  a écrit :
> >
> > > We need a tag for an RC in order to match a VOTE thread with the code
> > being
> > > proposed.
> > >
> > > Gary
> > >
> > > On Oct 22, 2017 10:24, "Romain Manni-Bucau" 
> > wrote:
> > >
> > > > Revision is r1812876.
> > > >
> > > > Have to admit im not sure about the hack to use to have a rc tag
> (name)
> > > > without rc artifacts which wouldnt match the target release with mvn
> > > > release plugin but dont think it is a blocker (but still happy to
> learn
> > > it
> > > > ;)).
> > > >
> > > > Le 22 oct. 2017 17:29, "Gary Gregory"  a
> > écrit :
> > > >
> > > > The tag name is wrong because it is not postfixed with RC2. All SVN
> > links
> > > > should be accompanied with a revision number.
> > > >
> > > > Gary
> > > >
> > > > On Oct 22, 2017 02:31, "Romain Manni-Bucau" 
> > > wrote:
> > > >
> > > > Hello guys,
> > > >
> > > > I would like to release the [jcs] component to resolve a cdi
> > > > performance issue (JCS-183) and a bug in dispose method when log are
> > > > in debug level (JCS-184).
> > > >
> > > >  Maven artifacts are at:
> > > > https://repository.apache.org/service/local/repositories/
> > > > orgapachecommons-1281/
> > > >
> > > >  The Subversion tag is:
> > > > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> > > commons-jcs-2.2.1/
> > > >
> > > >  The release notes are available at:
> > > > https://issues.apache.org/jira/projects/JCS/versions/12341663
> > > > https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE-NOTES.txt
> > > >
> > > >  The staged sources and binaries are available at
> > > > https://dist.apache.org/repos/dist/dev/commons/jcs/
> > > >
> > > >  Please review the release candidate and vote.
> > > >
> > > >[ ] +1 Release these artifacts
> > > >[ ] +-0 don't care
> > > >[ ] -1 I oppose this release because ${reason}
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau |  Blog | Old Blog | Github | LinkedIn
> > > >
> > > > 
> -
> > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > > For additional commands, e-mail: dev-h...@commons.apache.org
> > > >
> > >
> >
>

Re: [RDF] Commons release?

2017-10-24 Thread Gary Gregory 
Hopefully someone who is familiar with Commons RDF is reading this...

Gary

On Fri, Oct 20, 2017 at 2:25 PM, Aaron Coburn  wrote:

> Hello,
>
> I wanted to check in on the status of a 0.4.0 release of Commons RDF. It
> seems that all of the open PRs have been merged. Any idea on a timeframe
> for the next release?
>
> Thanks,
> Aaron
>
> On 9/19/17, 5:58 PM, "Aaron Coburn"  wrote:
>
> Sergio,
>
> Thanks! The LDP server implementation is spread across quite a few
> repositories in this github organization: https://github.com/trellis-ldp
> (everything is Apache2 licensed), but the core abstractions are found in:
>
> API: https://github.com/trellis-ldp/trellis-api
> SPI: https://github.com/trellis-ldp/trellis-spi
> HTTP layer: https://github.com/trellis-ldp/trellis-http
>
> Most of the components have already been released to maven central,
> but I'm still working on a few of them (particularly the HTTP layer and the
> persistence layer).
>
> The main difference between this and, say, Marmotta, is that this
> implementation is designed to scale horizontally. And by making use of
> Commons-RDF, the interfaces of this LDP server aren't tied to a particular
> RDF library implementation -- e.g. Jena or RDF4J -- though I do use Jena in
> the implementation code. I am also making significant use of ZooKeeper
> (Curator), Kafka and Beam.
>
> Aaron
>
> > On Sep 19, 2017, at 5:27 PM, Sergio Fernández 
> wrote:
> >
> > Hi Aaron,
> >
> > you're right, we have quite some things to release. But first I' d
> like to
> > take a look to our backlog, because we have some open PRs. Hopefully
> I'll
> > have some time later this week, at the latest on the weekend.
> >
> > Just for curiosity, can you provide us a pointer to your Commons
> RDF-based
> > LDP implementation?
> >
> > Thanks.
> >
> > Cheers,
> >
> >
> >
> > On Mon, Sep 18, 2017 at 2:24 PM, Aaron Coburn 
> wrote:
> >
> >> Hi!
> >>
> >> The last release of commons-rdf was from last November, and there
> are some
> >> nice features in the master branch that I would really like to use
> --
> >> especially the improved OSGi support. It seems that there are a few
> >> unresolved jira issues, such that this wouldn't be a 1.0 release,
> but even
> >> a 0.4.0 release would be great.
> >>
> >> As a little background, over the last several months I've built a
> server
> >> implementation of the W3C Linked Data Platform in which commons-rdf
> >> provides all of the core RDF abstractions.
> >>
> >> Would it be possible to move forward with a release? I would be
> more than
> >> happy to help out.
> >>
> >> Thanks,
> >> Aaron
> >>
> >> acob...@apache.org
> >> 
> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
>
> ?B�
> CB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��[[ۜ˘\?
> X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��[[ۜ˘\?X�?K�ܙ�B
>
>
>

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-24 Thread Gary Gregory 
Our process documented here http://commons.apache.org/releases/prepare.html
makes it pretty clear that the RC tag should be labeled as such and that a
tag like "commons-jcs-2.2.1" should only be created after a VOTE passes.

Gary

On Sun, Oct 22, 2017 at 3:17 PM, Romain Manni-Bucau 
wrote:

> So i just copy the mvn release tag? Sounds quite useless since the tag is
> done no?
>
> Le 22 oct. 2017 21:14, "Gary Gregory"  a écrit :
>
> > We need a tag for an RC in order to match a VOTE thread with the code
> being
> > proposed.
> >
> > Gary
> >
> > On Oct 22, 2017 10:24, "Romain Manni-Bucau" 
> wrote:
> >
> > > Revision is r1812876.
> > >
> > > Have to admit im not sure about the hack to use to have a rc tag (name)
> > > without rc artifacts which wouldnt match the target release with mvn
> > > release plugin but dont think it is a blocker (but still happy to learn
> > it
> > > ;)).
> > >
> > > Le 22 oct. 2017 17:29, "Gary Gregory"  a
> écrit :
> > >
> > > The tag name is wrong because it is not postfixed with RC2. All SVN
> links
> > > should be accompanied with a revision number.
> > >
> > > Gary
> > >
> > > On Oct 22, 2017 02:31, "Romain Manni-Bucau" 
> > wrote:
> > >
> > > Hello guys,
> > >
> > > I would like to release the [jcs] component to resolve a cdi
> > > performance issue (JCS-183) and a bug in dispose method when log are
> > > in debug level (JCS-184).
> > >
> > >  Maven artifacts are at:
> > > https://repository.apache.org/service/local/repositories/
> > > orgapachecommons-1281/
> > >
> > >  The Subversion tag is:
> > > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> > commons-jcs-2.2.1/
> > >
> > >  The release notes are available at:
> > > https://issues.apache.org/jira/projects/JCS/versions/12341663
> > > https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE-NOTES.txt
> > >
> > >  The staged sources and binaries are available at
> > > https://dist.apache.org/repos/dist/dev/commons/jcs/
> > >
> > >  Please review the release candidate and vote.
> > >
> > >[ ] +1 Release these artifacts
> > >[ ] +-0 don't care
> > >[ ] -1 I oppose this release because ${reason}
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau |  Blog | Old Blog | Github | LinkedIn
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > For additional commands, e-mail: dev-h...@commons.apache.org
> > >
> >
>

[VOTE] Release Apache Commons Pool 2.4.3 based on RC1

2017-10-24 Thread Gary Gregory 
We have fixed a few bugs since Apache Commons Pool 2.4.2 was released, so I
would like to release Apache Commons Pool 2.4.3.

Apache Commons Pool 2.4.3 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/pool at revision: 22662
Get it like this: svn co
https://dist.apache.org/repos/dist/dev/commons/pool

The tag is here:

https://git-wip-us.apache.org/repos/asf?p=commons-pool.git;a=tag;h=c893fa532be0b06e105d3a5adcb7d5fdd9cba979

Maven artifacts are here:

https://repository.apache.org/service/local/repositories/orgapachecommons-1284

These are the artifacts and their SHA1 hashes:

/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-javadoc.jar.asc
(SHA1: 1c3b8f36822f25880aaad2b148e98bdee898882a)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-test-sources.jar
(SHA1: 8894b161255af399029e30cf7a0add23d9b09ca6)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-bin.tar.gz
(SHA1: 6193d385d80d79a81e3d393c9aa1fb1b12cd)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-sources.jar
(SHA1: f25308f7512e59d78b24a058a30fc9d3af401690)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-tests.jar.asc
(SHA1: 2244c06e77d3424d930893b8e4884f804654e828)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-javadoc.jar
(SHA1: 6ec182b30e2148b1295c2024c6fac3a1c568)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-bin.tar.gz.asc
(SHA1: a9c685d6191d09ea2c7d82beca82a813a0aa1613)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-src.tar.gz
(SHA1: 688a1b5bc9011f27197423a1ffe0c3aeacbbfceb)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-test-sources.jar.asc
(SHA1: 3a8d18397c140a63b1ffdbe74e8fa2f3a2732f9c)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-src.tar.gz.asc
(SHA1: 347b72198684885faeb262f48457a8270d5125b0)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-bin.zip
(SHA1: dd5f761b471bbd7481955d6e5f64c6b6ea1c97e2)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3.jar.asc
(SHA1: f1734672cc7200780e0b3fcb785d12398bee8af3)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3.pom
(SHA1: b5813ddd4dd19ac6809bacbb54cbfb2d35a8df73)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-src.zip.asc
(SHA1: aaa30959ddbf184fff7e1ab22cc1a3b4a4ee87a0)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-bin.zip.asc
(SHA1: eae94976483c0958ade6e10e834095fea349e5b0)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3.pom.asc
(SHA1: 37879823c0428d906ad9acaf3770aad48fa950d8)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-sources.jar.asc
(SHA1: 3153937a96a7828ea080888b8e02151662e9cce2)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-src.zip
(SHA1: 2ea2a543889f2011e3d73a8f579cfeece8efb600)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3.jar
(SHA1: e7ab2a5143cb4e0b21d8ca81c265095e4567dd22)
/org/apache/commons/commons-pool2/2.4.3/commons-pool2-2.4.3-tests.jar
(SHA1: 795621ba371106cf1043c1b8520998e9d4e175a3)

I tested this RC using 'mvn clean verify' on Microsoft Windows [Version
10.0.16299.19] with:

- Oracle Java 6
- Oracle Java 7
- Oracle Java 8
- Oracle Java 9: To run the build on Oracle Java 9, you need to override
the Maven Animal Sniffer plugin with 'mvn -V clean verify
-Dcommons.animal-sniffer.version=1.16'
- IBM Java 8

Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
06:51:28-0700)
Maven home: C:\Java\apache-maven-3.0.5
Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_45\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 8", version: "6.2", arch: "amd64", family: "windows"

Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T01:58:13-06:00)
Maven home: C:\Java\apache-maven-3.5.2\bin\..
Java version: 1.7.0_80, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_80\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"

Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T01:58:13-06:00)
Maven home: C:\Java\apache-maven-3.5.2\bin\..
Java version: 1.8.0_144, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_144\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T01:58:13-06:00)
Maven home: C:\Java\apache-maven-3.5.2\bin\..
Java version: 9.0.1, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk-9.0.1
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T01:58:13-06:00)
Maven home: C:\Java\apache-maven-3.5.2\bin\..
Java version: 1.8.0, vendor: IBM Corporation
Java home:

[GitHub] commons-cli pull request #21: Add module-info

2017-10-24 Thread michaelsavich 
GitHub user michaelsavich opened a pull request:

https://github.com/apache/commons-cli/pull/21

Add module-info

This should modularize commons-cli. We may have to do another commit to get 
maven to build modularized jars by default, but as of this build javac works 
perfectly.

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

$ git pull https://github.com/michaelsavich/commons-cli master

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

https://github.com/apache/commons-cli/pull/21.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 #21






---

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

Re: [collections] release 4.2

2017-10-24 Thread Gary Gregory 
As long as it is on your to-do list, I can focus on other tasks.

Thank you!
Gary

On Oct 24, 2017 13:29, "Benedikt Ritter"  wrote:

> I‘m planning to work on it soon but I can‘t give you an ETA at the moment.
>
> Regards,
> Benedikt
>
> Gary Gregory  schrieb am Di. 24. Okt. 2017 um
> 00:01:
>
> > We've had a couple of false starts here. Is the RM ready to fire off an
> RC?
> >
> > Gary
> >
>

Re: [collections] release 4.2

2017-10-24 Thread Benedikt Ritter 
I‘m planning to work on it soon but I can‘t give you an ETA at the moment.

Regards,
Benedikt

Gary Gregory  schrieb am Di. 24. Okt. 2017 um 00:01:

> We've had a couple of false starts here. Is the RM ready to fire off an RC?
>
> Gary
>

Re: [pool] Java 7 and release

2017-10-24 Thread sebb 
On 24 October 2017 at 15:22, Gary Gregory  wrote:
> I think I will:
> - release pool
> - update to Java 7

Might be sensible to add a note to the pom that Tomcat 8 needs Java 7+.
This means that Pool 2 cannot be updated beyond Java 7 without
affecting Tomcat 8.

> It seems cleaner that way.
>
> Gary
>
> On Tue, Oct 24, 2017 at 8:04 AM, Matt Sicker  wrote:
>
>> On 24 October 2017 at 06:44, Mark Thomas  wrote:
>>
>> > On 24/10/17 05:56, Matt Sicker wrote:
>> > > Go for it! Though perhaps some quick feedback from Tomcat would be good
>> > > since they're the primary Apache project that uses the library.
>> >
>> > I assume we are talking about Pool 2.x.
>> >
>>
>> Yes.
>>
>>
>> > Pool 2.x is used by Tomcat 8 onwards and Tomcat 8 has a requirement of
>> > Java 7 or later so updating Pool 2.x to Java 7 would not present a
>> > problem for the Tomcat community.
>> >
>>
>> Great! That means DBCP 2.x should be able to upgrade to Java 7 as well if
>> it hasn't already.
>>
>> --
>> Matt Sicker 
>>

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

Re: [pool] Java 7 and release

2017-10-24 Thread Gary Gregory 
I think I will:
- release pool
- update to Java 7

It seems cleaner that way.

Gary

On Tue, Oct 24, 2017 at 8:04 AM, Matt Sicker  wrote:

> On 24 October 2017 at 06:44, Mark Thomas  wrote:
>
> > On 24/10/17 05:56, Matt Sicker wrote:
> > > Go for it! Though perhaps some quick feedback from Tomcat would be good
> > > since they're the primary Apache project that uses the library.
> >
> > I assume we are talking about Pool 2.x.
> >
>
> Yes.
>
>
> > Pool 2.x is used by Tomcat 8 onwards and Tomcat 8 has a requirement of
> > Java 7 or later so updating Pool 2.x to Java 7 would not present a
> > problem for the Tomcat community.
> >
>
> Great! That means DBCP 2.x should be able to upgrade to Java 7 as well if
> it hasn't already.
>
> --
> Matt Sicker 
>

Re: [pool] Java 7 and release

2017-10-24 Thread Matt Sicker 
On 24 October 2017 at 06:44, Mark Thomas  wrote:

> On 24/10/17 05:56, Matt Sicker wrote:
> > Go for it! Though perhaps some quick feedback from Tomcat would be good
> > since they're the primary Apache project that uses the library.
>
> I assume we are talking about Pool 2.x.
>

Yes.


> Pool 2.x is used by Tomcat 8 onwards and Tomcat 8 has a requirement of
> Java 7 or later so updating Pool 2.x to Java 7 would not present a
> problem for the Tomcat community.
>

Great! That means DBCP 2.x should be able to upgrade to Java 7 as well if
it hasn't already.

-- 
Matt Sicker

Re: [pool] Java 7 and release

2017-10-24 Thread Mark Thomas 
On 24/10/17 05:56, Matt Sicker wrote:
> Go for it! Though perhaps some quick feedback from Tomcat would be good
> since they're the primary Apache project that uses the library.

I assume we are talking about Pool 2.x.

Pool 2.x is used by Tomcat 8 onwards and Tomcat 8 has a requirement of
Java 7 or later so updating Pool 2.x to Java 7 would not present a
problem for the Tomcat community.

Mark


> 
> On 23 October 2017 at 17:30, Gary Gregory  wrote:
> 
>> Or the other way around. Release and update to Java 7...
>>
>> Gary
>>
>> On Mon, Oct 23, 2017 at 4:25 PM, Gary Gregory 
>> wrote:
>>
>>> Wow, 2 years since the last release of [pool]. I plan on updating to Java
>>> 7 and push out a release.
>>>
>>> Gary
>>>
>>
> 
> 
> 


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

Re: [pool] Java 7 and release

2017-10-24 Thread Jochen Wiedmann 
On Tue, Oct 24, 2017 at 12:30 AM, Gary Gregory  wrote:
> Or the other way around. Release and update to Java 7...

Sounds like a better plan to me. After two years, it could be
necessary to provide another maintenance release at any time.

Jochen


-- 
The next time you hear: "Don't reinvent the wheel!"

http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg

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