I posted some background why Maven currently uses the no-AOP build in https://github.com/apache/maven/pull/169#issuecomment-396177378
On 10 June 2018 at 19:42, Michael Osipov <[email protected]> wrote: > Am 2018-06-10 um 15:45 schrieb Robert Scholte: > >> I'm a bit worried about the no_aop drop. I'm pretty sure Stuart would >> have noticed this in the past. >> I'm very proud we can say that even Maven 3.0 still runs on the latest >> JDK version, introducing bytecode parsers like ASM might block this benefit >> with future versions. Don't think we need it. >> > > I did not drop the no_aop. I upgraded just the version. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
