Romain, I have enabled JUnit5 5.6.0/1.6.0-SNAPSHOT.
I want to know if the bug OSSRH-51220 is fixed.
https://builds.apache.org/job/maven-box/job/maven-surefire/job/junit5-snapshots/

On Sat, Oct 12, 2019 at 12:10 PM Tibor Digana <tibordig...@apache.org>
wrote:

> Here is the pull request
> https://github.com/codehaus-plexus/plexus-languages/pull/29
>
> On Sat, Oct 12, 2019 at 11:49 AM Romain Manni-Bucau <rmannibu...@gmail.com>
> wrote:
>
>> I understand and if we can we must do but not a blocker - was my point
>> Also keep in mind we could do the update automatically with asm versioning
>> scheme using our resolver in the mojo.
>> So let's fix issues for most users - once again j > 11 is a play area, not
>> for prod today - and maybe enhance our asm integration layer later.
>>
>> Le sam. 12 oct. 2019 à 11:42, Tibor Digana <tibordig...@apache.org> a
>> écrit :
>>
>> > all bad, see the stackoverflow. It happens that the users argue that
>> they
>> > have to update our dependencies which is our responsibility!
>> >
>> > On Sat, Oct 12, 2019 at 11:40 AM Romain Manni-Bucau <
>> rmannibu...@gmail.com
>> > >
>> > wrote:
>> >
>> > > Dont think there is an api version upgrade between 7.0 and 7.2 so can
>> be
>> > > upgraded in user pom so not a blocker for a milestone release
>> IMHO....j13
>> > > and j14 are still not adopted too so all good.
>> > >
>> > > Le sam. 12 oct. 2019 à 11:35, Tibor Digana <tibordig...@apache.org> a
>> > > écrit :
>> > >
>> > > > We still use plexus-java:1.0.3 which depends on ASM 7.0.
>> > > > The support for JDk 13 and 14 is in the version 7.2.
>> > > > We have similar upgrade in
>> > > > https://github.com/apache/maven-shade-plugin/pull/29
>> > > >
>> > > > On Thu, Oct 10, 2019 at 2:53 AM Olivier Lamy <ol...@apache.org>
>> wrote:
>> > > >
>> > > > > Hi,
>> > > > > It's now almost 10 months since last and around 30 issues fixed.
>> > > > > Maybe time for a new release?
>> > > > > Moving issues still open to 3.0.0-M5?
>> > > > >
>> > > > > cheers
>> > > > > --
>> > > > > Olivier Lamy
>> > > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> > > > >
>> > > >
>> > >
>> >
>>
>

Reply via email to