Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
In-Reply-To: <00c401d1cb49$83643a50$8a2caef0$@cs.washington.edu>
References: <CAB917R+7gtwhL0OeqEzqGG-YNAvmvvJev9j3Ksu12juHDfZ7TQ@mail.gmail.com>
 <00c401d1cb49$83643a50$8a2caef0$@cs.washington.edu>
From: sebb <sebbaz@gmail.com>
Date: Tue, 21 Jun 2016 01:15:00 +0100
Message-ID: <CAOGo0Va+pbTP8ZGi1yL8wNaSKuBcF7T7cqAFDZ-y=35DMNJGnQ@mail.gmail.com>
Subject: Re: [VOTE] Release Apache Commons BCEL 6.0 based on RC6
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=UTF-8
archived-at: Tue, 21 Jun 2016 00:15:14 -0000

On 21 June 2016 at 00:14, Mark Roberts <markro@cs.washington.edu> wrote:
> Sorry - I'm replying to my own post.  Is there any chance that there is a revision point in the active tree that corresponds exactly to RC6 but without the path changes?  I could do some testing on that.

I don't think so; there were some subsequent fixes

> Probably too much to hope for.

However, it's pretty easy to use the Maven Shade plugin to produce an
updated version of the jar with the changed package names.

I'll email you a copy of a pom under separate cover.

> Thanks,
> Mark
>
>> -----Original Message-----
>> From: Mark Roberts [mailto:markro@cs.washington.edu]
>> Sent: Monday, June 20, 2016 4:12 PM
>> To: 'Commons Developers List'
>> Cc: 'findbugs-discuss@cs.umd.edu'; 'findbugs-core@lists.sourceforge.net'
>> Subject: RE: [VOTE] Release Apache Commons BCEL 6.0 based on RC6
>>
>> Well I was clearly confused about this release.  It has reverted back to the old
>> class hierarchy in the name of binary compatibility.  I can see now that that
>> was the intention and it makes sense.  However, I cannot test it (and hence
>> vote up or down) as I am certainly not going to edit all my sources back to the
>> 'old' system.
>>
>> So my question is what is the plan?  This release gets me no closer to a place
>> where I can quit providing my own version of BCEL with our Daikon product.
>> What is the plan for a release from the active tree with the new class
>> hierarchy?
>>
>> Thank you,
>> Mark Roberts
>>
>>
>> > -----Original Message-----
>> > From: Benedikt Ritter [mailto:britter@apache.org]
>> > Sent: Monday, June 20, 2016 12:37 PM
>> > To: Commons Developers List
>> > Cc: findbugs-discuss@cs.umd.edu; findbugs-core@lists.sourceforge.net
>> > Subject: [VOTE] Release Apache Commons BCEL 6.0 based on RC6
>> >
>> > Hi,
>> >
>> > after some build related problems with RC5, I'd like to call a vote to
>> > release Apache Commons BCEL 6.0 based on RC6. The only changes
>> > compared to
>> > RC5 is a fix in the source assembly: It now includes all files
>> > necessary to run a clean build.
>> >
>> > BCEL 6.0 RC6 is available for review here:
>> >   https://dist.apache.org/repos/dist/dev/commons/bcel (rev 14065)
>> >
>> > The tag is here:
>> >
>> >
>> https://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_0_R
>> > C6
>> >  (rev 1749388)
>> >
>> > Maven artifacts are here:
>> >
>> > https://repository.apache.org/content/repositories/orgapachecommons-
>> > 1179/org/apache/bcel/bcel/6.0/
>> >
>> > These are the Maven artifacts and their hashes:
>> >
>> > bcel-6.0-javadoc.jar
>> > (SHA1: 89cf95656f0f8a93e77100c8d5811f7cd9af866b)
>> > bcel-6.0-sources.jar
>> > (SHA1: 162f96530e8935e8a71a9e6d5497026aa3bdc945)
>> > bcel-6.0-test-sources.jar
>> > (SHA1: 2b07be3a0a4560c9766d3261cd012cf636fe965a)
>> > bcel-6.0-tests.jar
>> > (SHA1: 9e825da46e0cd66f87ccd907a43c4e2ebd15b8d6)
>> > bcel-6.0.jar
>> > (SHA1: 09d0a4c32ba6c3c22f0680f89ceeaf3e677ac659)
>> > bcel-6.0.pom
>> > (SHA1: a5d48ac34909f3a0ac788d37835075be5c2bb9d7)
>> >
>> > I have tested this with Java 7 and 8 using Maven 3.3.9 on Mac OS 10.11.5.
>> >
>> > Details of changes since 5.2 are in the release notes:
>> >   https://dist.apache.org/repos/dist/dev/commons/bcel/RELEASE-
>> NOTES.txt
>> >   http://home.apache.org/~britter/commons/bcel/6.0-RC6/changes-
>> > report.html
>> >
>> > Site:
>> >   http://home.apache.org/~britter/commons/bcel/6.0-RC6/
>> > (note some *relative* links are broken and the 6.0 directories are not
>> > yet created - these will be OK once the site is deployed)
>> >
>> > Clirr Report (compared to 5.2):
>> >
>> > http://home.apache.org/~britter/commons/bcel/6.0-RC6/clirr-report.html
>> >
>> > Note that Clirr reports several errors. These have been discussed on
>> > the ML already and I uploaded the site a while ago giving everybody
>> > the opportunity to raise objections against these changes. These
>> > changes are also explicitly noted in the Release notes.
>> >
>> > Furthermore java.io.Serializable has been dropped from all BCEL
>> > classes. An extended Clirr report including this change can be reviewed
>> here:
>> >
>> > http://home.apache.org/~britter/commons/bcel/6.0-RC6/bcel5-bcel6-clirr
>> > -
>> > report.html
>> >
>> > We don't consider this to be a problem because we don't see a reason
>> > for users to serialize BCEL classes.
>> >
>> > RAT Report:
>> >
>> > http://home.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 2016
>> >
>> > [ ] +1 Release these artifacts
>> > [ ] +0 OK, but...
>> > [ ] -0 OK, but really should fix...
>> > [ ] -1 I oppose this release because...
>> >
>> > We're almost there... :-)
>> > Thanks!
>> > Benedikt
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

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