commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [VOTE] Release BCEL 6.0 based on RC3
Date Fri, 13 Mar 2015 21:18:45 GMT
On 13 March 2015 at 17:40, Sarah Murray <sarahkm1972@gmail.com> wrote:
> It's absurd to have a library where no released version works on any
> supported version of Java. End of story

Well, there are 2 solutions to that.

1) BCEL is abandoned/retired.
2) BCEL is updated to support recent versions of Java.

> On Wed, Mar 11, 2015 at 7:04 PM, sebb <sebbaz@gmail.com> wrote:
>
>> On 12 March 2015 at 01:25, Niall Pemberton <niall.pemberton@gmail.com>
>> wrote:
>> > On Fri, Mar 6, 2015 at 7:42 PM, sarahkm1972 <sarahkm1972@gmail.com>
>> wrote:
>> >
>> >> +100 to RERO. +1000 to release before we're all dead. It's been a decade
>> >> people. Just cut a release already. You can always cut another one
>> later.
>> >> Stop with the excuses
>> >>
>> >> Whatever you want to call it - alpha, beta, RC, final, anything. Java 8
>> >> users are left in a lurch. Compiling libraries is not a realistic
>> solution.
>> >> As stated previously by others we would also have to patch and compile
>> >> libraries depending on BCEL and also figure the transitive dependency
>> graph
>> >> for everything we use since we can't use Maven to do that due to BCEL
>> not
>> >> being in Maven. This is a huge huge pain because we're big Scala users
>> and
>> >> rely heavily on the Typesafe ecosystem which is dropping support for
>> Java 7
>> >> in all of its products and already has in Play Framework and Akka as
>> well
>> >> as
>> >> others like its Config library.
>> >>
>> >
>> > You say "stop with the excuses" and then go on to list a whole bunch of
>> > excuses why its too much effort for you to build BCEL and test it. Yes it
>> > would be an effort - but it would be invaluable to have some pre-release
>> > testing and feedback and help to get it our faster.
>>
>> It's not even necessary to build BCEL in order to test against trunk,
>> because you can get BCEL snapshots from the Apache Maven Snapshot
>> repository.
>> If the CI system is working, the SNAPSHOTs wll be updated regularly
>> when there have been commits.
>> If it appears that the snapshot has not been built for some while
>> since the last commit (e.g. 24 hrs), ask here and someone can prod the
>> CI system (or just deploy another snapshot).
>>
>> Of course such builds have no guarantees, and should not be relied on
>> long-term (they may be replaced at any time), but for test purposes
>> they will do.
>>
>> > Niall
>> >
>> >
>> >
>> >> --S.
>> >>
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://apache-commons.680414.n4.nabble.com/VOTE-Release-BCEL-6-0-based-on-RC3-tp4667129p4673474.html
>> >> Sent from the Commons - Dev mailing list archive at Nabble.com.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>

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


Mime
View raw message