Re: [BCEL] 5.3 is going to be messy

> > > So? What's your point there? > > Commons libraries are generally very low level, and are often embedded > deep within software stacks. > > So changes which require downstream changes are expensive when > considered as a whole. > > This is very different from many other ASF projects which can

Re: [BCEL] 5.3 is going to be messy

On 8 June 2016 at 00:56, Torsten Curdt wrote: >> >> >> 1) I don't believe we should force users to migrate their code in >> >> order to support java 7/8. >> >> >> > >> > ...and that line of thinking is why it feels like commons projects are >> > effectively stuck in the past. >> >> And maybe the e

Re: [BCEL] 5.3 is going to be messy

> > >> 1) I don't believe we should force users to migrate their code in > >> order to support java 7/8. > >> > > > > ...and that line of thinking is why it feels like commons projects are > > effectively stuck in the past. > > And maybe the ease of upgrade is why they are popular with users. > We

Re: [BCEL] 5.3 is going to be messy

On Jun 7, 2016 3:17 AM, "Torsten Curdt" wrote: > > > > > 1) I don't believe we should force users to migrate their code in > > order to support java 7/8. > > > > ...and that line of thinking is why it feels like commons projects are > effectively stuck in the past. +1! > > No one needs to upgrad

Re: [BCEL] Revert package rename in trunk (Was: [BCEL] 5.3 is going to be messy)

Andrey Loskutov schrieb am Di., 7. Juni 2016 um 19:49 Uhr: > On Tuesday 07 June 2016 17:01 Benedikt Ritter wrote: > > Okay. > > > > - I'm going to revert the package rename. > > - We're going to create a binary compatible release for Java 7 and Java 8 > > support. > > - We will bump the major ver

Re: [BCEL] Revert package rename in trunk (Was: [BCEL] 5.3 is going to be messy)

On Tuesday 07 June 2016 17:01 Benedikt Ritter wrote: > Okay. > > - I'm going to revert the package rename. > - We're going to create a binary compatible release for Java 7 and Java 8 > support. > - We will bump the major version number to indicate that there are massive > changes in this release.

Re: [BCEL] Revert package rename in trunk (Was: [BCEL] 5.3 is going to be messy)

t; >> Benedikt >> >> >> >> -- Forwarded message - >> >> From: Andrey Loskutov >> >> Date: Di., 7. Juni 2016 um 17:55 Uhr >> >> Subject: Re: [BCEL] 5.3 is going to be messy >> >> To: >> >> Cc: B

Re: [BCEL] Revert package rename in trunk (Was: [BCEL] 5.3 is going to be messy)

e in trunk back to > >> org.apache.bcel ? (For reasons see below) > >> > >> Benedikt > >> > >> -- Forwarded message ----- > >> From: Andrey Loskutov > >> Date: Di., 7. Juni 2016 um 17:55 Uhr > >> Subject: Re: [BCEL] 5.3 is going to

Re: [BCEL] Revert package rename in trunk (Was: [BCEL] 5.3 is going to be messy)

reasons see below) >> >> Benedikt >> >> -- Forwarded message - >> From: Andrey Loskutov >> Date: Di., 7. Juni 2016 um 17:55 Uhr >> Subject: Re: [BCEL] 5.3 is going to be messy >> To: >> Cc: Benedikt Ritter >> >> >> On Tu

Re: [BCEL] Revert package rename in trunk (Was: [BCEL] 5.3 is going to be messy)

Date: Di., 7. Juni 2016 um 17:55 Uhr > Subject: Re: [BCEL] 5.3 is going to be messy > To: > Cc: Benedikt Ritter > > > On Tuesday 07 June 2016 15:37 Benedikt Ritter wrote: >> > > I propose we create the 5.x branch now. Those who want/need a > compatible >>

[BCEL] Revert package rename in trunk (Was: [BCEL] 5.3 is going to be messy)

Hi, any objections against reverting the package rename in trunk back to org.apache.bcel ? (For reasons see below) Benedikt -- Forwarded message - From: Andrey Loskutov Date: Di., 7. Juni 2016 um 17:55 Uhr Subject: Re: [BCEL] 5.3 is going to be messy To: Cc: Benedikt Ritter

Re: [BCEL] 5.3 is going to be messy

On Tuesday 07 June 2016 15:37 Benedikt Ritter wrote: > > > I propose we create the 5.x branch now. Those who want/need a compatible > > > release can work that out in that branch. All others can work on trunk to > > > get BCEL 6 out of the door with Java 7 and Java 8 compatibility. > > > > Sorry, I

Re: [BCEL] 5.3 is going to be messy

Hello, Andrey Loskutov schrieb am Di., 7. Juni 2016 um 17:35 Uhr: > On Tuesday 07 June 2016 15:24 Benedikt Ritter wrote: > > Hi, > > > > sebb schrieb am Di., 7. Juni 2016 um 11:49 Uhr: > > > 0) I think we are fairly close to being able to release compatible > > > code with all the necessary fix

Re: [BCEL] 5.3 is going to be messy

On Tuesday 07 June 2016 15:24 Benedikt Ritter wrote: > Hi, > > sebb schrieb am Di., 7. Juni 2016 um 11:49 Uhr: > > 0) I think we are fairly close to being able to release compatible > > code with all the necessary fixes > > > > 1) I don't believe we should force users to migrate their code in > >

Re: [BCEL] 5.3 is going to be messy

I suspect Gary wants a 5.3 release because the CLIRR Maven plugin fails in Java 8 which has resulted in https://github.com/mojohaus/clirr-maven-plugin/issues/3 , LANG-1025, and WICKET-5836 among others. We ran into this in Log4j, which I a

Re: [BCEL] 5.3 is going to be messy

Hi, sebb schrieb am Di., 7. Juni 2016 um 11:49 Uhr: > On 6 June 2016 at 21:02, Gary Gregory wrote: > > On Mon, Jun 6, 2016 at 12:44 PM, Benedikt Ritter > wrote: > > > >> Hi all, > >> > >> I had a brief look at the state of BCEL wrt doing a last 5.x release. > Well, > >> it feels like that is g

Re: [BCEL] 5.3 is going to be messy

On 7 June 2016 at 14:29, Dave Brosius wrote: > > > On 06/07/2016 06:39 AM, sebb wrote: >> >> On 7 June 2016 at 11:15, Torsten Curdt wrote: 1) I don't believe we should force users to migrate their code in order to support java 7/8. >>> ...and that line of thinking is why it fe

Re: [BCEL] 5.3 is going to be messy

On 06/07/2016 06:39 AM, sebb wrote: On 7 June 2016 at 11:15, Torsten Curdt wrote: 1) I don't believe we should force users to migrate their code in order to support java 7/8. ...and that line of thinking is why it feels like commons projects are effectively stuck in the past. And maybe the

Re: [BCEL] 5.3 is going to be messy

On Tue, 7 Jun 2016 11:39:09 +0100, sebb wrote: On 7 June 2016 at 11:15, Torsten Curdt wrote: 1) I don't believe we should force users to migrate their code in order to support java 7/8. ...and that line of thinking is why it feels like commons projects are effectively stuck in the past.

Re: [BCEL] 5.3 is going to be messy

+1 Torsten On Tue, Jun 7, 2016 at 6:17 AM Torsten Curdt wrote: > > > > 1) I don't believe we should force users to migrate their code in > > order to support java 7/8. > > > > ...and that line of thinking is why it feels like commons projects are > effectively stuck in the past. > > No one needs

Re: [BCEL] 5.3 is going to be messy

On 7 June 2016 at 11:15, Torsten Curdt wrote: >> >> 1) I don't believe we should force users to migrate their code in >> order to support java 7/8. >> > > ...and that line of thinking is why it feels like commons projects are > effectively stuck in the past. And maybe the ease of upgrade is why t

Re: [BCEL] 5.3 is going to be messy

> > 1) I don't believe we should force users to migrate their code in > order to support java 7/8. > ...and that line of thinking is why it feels like commons projects are effectively stuck in the past. No one needs to upgrade. If your projects live in the past - there are bug fix releases. But i

Re: [BCEL] 5.3 is going to be messy

On 6 June 2016 at 21:02, Gary Gregory wrote: > On Mon, Jun 6, 2016 at 12:44 PM, Benedikt Ritter wrote: > >> Hi all, >> >> I had a brief look at the state of BCEL wrt doing a last 5.x release. Well, >> it feels like that is going to be a mess: >> >> - We have @since 6.0 annotations all over the co

Re: [BCEL] 5.3 is going to be messy

On Mon, Jun 6, 2016 at 1:02 PM, Gary Gregory wrote: > On Mon, Jun 6, 2016 at 12:44 PM, Benedikt Ritter > wrote: > >> Hi all, >> >> I had a brief look at the state of BCEL wrt doing a last 5.x release. >> Well, >> it feels like that is going to be a mess: >> >> - We have @since 6.0 annotations al

Re: [BCEL] 5.3 is going to be messy

Gary Gregory wrote: > On Mon, Jun 6, 2016 at 12:44 PM, Benedikt Ritter > wrote: > >> Hi all, >> >> I had a brief look at the state of BCEL wrt doing a last 5.x release. >> Well, it feels like that is going to be a mess: >> >> - We have @since 6.0 annotations all over the code. >> - We have same

Re: [BCEL] 5.3 is going to be messy

On Mon, Jun 6, 2016 at 12:44 PM, Benedikt Ritter wrote: > Hi all, > > I had a brief look at the state of BCEL wrt doing a last 5.x release. Well, > it feels like that is going to be a mess: > > - We have @since 6.0 annotations all over the code. > - We have same deprecated classes - why if the co

[BCEL] 5.3 is going to be messy

Hi all, I had a brief look at the state of BCEL wrt doing a last 5.x release. Well, it feels like that is going to be a mess: - We have @since 6.0 annotations all over the code. - We have same deprecated classes - why if the code is currently in the shape for the 6.0 release, there should be no d