Great news!
Thanks Benedikt & everyone helped this release to appear after so long period
of silence!
Kind regards,
Andrey Loskutov
http://google.com/+AndreyLoskutov
> Gesendet: Freitag, 15. Juli 2016 um 08:28 Uhr
> Von: "Benedikt Ritter"
> An: "Commons Developers
/~britter/commons/bcel/6.0-RC7/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. sometime after 21:00 CEST 05-July
>
+1000.
I joined the commons list only because I wanted to listen to BCEL project.
Kind regards,
Andrey Loskutov
http://google.com/+AndreyLoskutov
> Gesendet: Freitag, 24. Juni 2016 um 11:35 Uhr
> Von: "Jochen Wiedmann"
> An: "Apache Commons Developers List"
&g
.apache.org/~britter/commons/bcel/6.0-RC6/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. sometime after 22:00 CEST 23-June 2
Hi,
Thanks & congratulations to BCEL team!
With this BCEL version all FB regression tests on both Java 8 and Java 9 (as
runtime) pass. Well done!
If I could vote, I would vote +1.
P.S:
Since we had this weekend also an official ASM 6 alpha release (see
http://mail.ow2.org/wws/arc/asm/2016-06/
gt; > > the current state of the code base and report any issues you see.
>> > >
>> > > Thank you!
>> > > Benedikt
>> >
>> >
>> >
>---------
>
implementers of this
* interface outside of the framework will be broken in future
* releases when methods are added to this interface.
*
* @since 1.0
*
*/
public interface IVetoableValue extends IObservableValue {
Kind regards,
Andrey Loskutov
http://google.com/+AndreyLoskutov
>
> From: "Benedikt Ritter"
> To: "Commons Developers List"
> Subject: Re: Re: [BCEL] Latest Clirr report
> > So from my limited FindBugs point of view we can release BCEL6 as it is
> > today on trunk.
> >
>
> Okay, so you would like to see an RC with the current state of trunk?!
Sure. Sooner is
is the BCEL API state we "exported" to downstream since 3 years :-(
Kind regards,
Andrey Loskutov
http://google.com/+AndreyLoskutov
> Gesendet: Sonntag, 12. Juni 2016 um 14:12 Uhr
> Von: sebb
> An: "Commons Developers List"
> Betreff: Re: [BCEL] Latest Clirr re
t our tests are
failing, see https://issues.apache.org/jira/browse/BCEL-273.
I'm working on fixing them and will be back if I will find something to fix on
BCEL side.
Thanks all for the feedback & support!
On Wednesday 08 June 2016 10:46 sebb wrote:
> On 8 June 2016 at 10:34, Andre
On Wednesday 08 June 2016 10:17 sebb wrote:
> OK, so what options are there?
>
> A) add the classes back in, but deprecate the class(es) and defer to
> the new implementation if possible
> B) Update Findbugs to use the new design
>
> Anything else?
>
> ==
>
> If the choice is between A and B, t
On Wednesday 08 June 2016 08:37 Benedikt Ritter wrote:
> Hallo Andrey,
>
> Andrey Loskutov schrieb am Mi., 8. Juni 2016 um 09:36 Uhr:
>
> > Hi,
> >
> > I'm following the package rename and trying to fix compile issues with
> > BCEL6 in FindBugs.
&g
Hi,
I'm following the package rename and trying to fix compile issues with BCEL6 in
FindBugs.
Before 6.0 we had both StackMap and StackMapTable classes (with StackMapEntry /
StackMapTableEntry elements).
This was added via https://issues.apache.org/jira/browse/BCEL-92 to support
Java 6.
Now i
Hi all,
following on the recent discussion and on the recent mails regarding the
keeping the "old" BCEL namespace for 6.0 I just wanted to share my view on the
BCEL API compatibility story, both from the API contributor/consumer sides,
since I'm playing both roles in projects below.
###
TL;DR
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.
On Tuesday 07 June 2016 17:26 sebb wrote:
> On 7 June 2016 at 17:18, Andrey Loskutov wrote:
> > On Tuesday 07 June 2016 17:15 sebb wrote:
> >> There have been quite a lot of changes to BCEL since 5.2.
> >>
> >> Lots of places currently mention 6.0 (@since; JIR
On Tuesday 07 June 2016 17:15 sebb wrote:
> There have been quite a lot of changes to BCEL since 5.2.
>
> Lots of places currently mention 6.0 (@since; JIRA; probably elsewhere).
>
> So whilst 5.3 might be OK as the next release version, it's going to
> be a lot of work to change all the referenc
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
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
> >
On Tuesday 07 June 2016 15:25 Benedikt Ritter wrote:
> Hello Andrey,
>
> Andrey Loskutov schrieb am Di., 7. Juni 2016 um 17:19 Uhr:
>
> > On Tuesday 07 June 2016 15:10 Benedikt Ritter wrote:
> > > Hello Andrey,
> > >
> > > right now I think it would
t an easy task, please focus resources on release.
> Benedikt
>
> Andrey Loskutov schrieb am Di., 7. Juni 2016 um 10:40 Uhr:
>
> > Hi all,
> >
> > I'm not a BCEL developer, just a user, but may I trigger a discussion to
> > move BCEL development from SVN t
s definitely a
time saver, not mentioning here all other benefits Git offers over SVN.
Comments?
[1] https://github.com/iloveeclipse/commons-bcel/commits/trunk
--
Kind regards,
Andrey Loskutov
http://google.com/+AndreyLoskutov
---
from the BCEL community on the upcoming BCEL 6
release compatibility story.
Please see my answers inline.
On Monday 06 June 2016 17:30 sebb wrote:
> On 6 June 2016 at 16:23, Andrey Loskutov wrote:
> > Hi all,
> >
> > here is the current state of FindBugs adoption to J
23 matches
Mail list logo
