Confirmed, thank you for the fix! Eagerly awaiting the release. On Mar 27, 2014, at 1:16 PM, Mirko Friedenhagen <[email protected]> wrote:
> Steven, > > thanks, I now could reproduce this. Installing a local SNAPSHOT of the > shared library and plugin did resolve this. > So I guess we have to release both pretty soon :-). > Regards Mirko > -- > http://illegalstateexception.blogspot.com/ > https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) > https://bitbucket.org/mfriedenhagen/ > > > On Thu, Mar 27, 2014 at 8:37 PM, Steven Schlansker > <[email protected]> wrote: >> Here is a reproduction case: >> >> https://github.com/stevenschlansker/mdep-439-analyze-java8 >> >> On Mar 27, 2014, at 10:26 AM, Mirko Friedenhagen <[email protected]> >> wrote: >> >>> Steven, I can not reproduce that maven-dependency-plugin:analyze:2.8 >>> fails with JDK8. I have created a small library with a Lambda (call it >>> L) and ran dependency:analyze without probems. I installed this >>> library and made a new component depend on L and ran >>> dependency:analyze successfully again. As stated in MDEP-439[1], can >>> you or someone else provide a sample? Otherwise I will close this bug. >>> >>> [1] http://jira.codehaus.org/browse/MDEP-439 >>> Regards Mirko >>> -- >>> http://illegalstateexception.blogspot.com/ >>> https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) >>> https://bitbucket.org/mfriedenhagen/ >>> >>> >>> On Thu, Mar 27, 2014 at 1:28 PM, Matt Benson <[email protected]> wrote: >>>> Oh, good news on the dependency plugin bit--I almost forgot that you had >>>> mentioned its underlying library having already upgraded its trunk to >>>> version 4. I was thinking more about jdependency, which supports the shade >>>> plugin. >>>> >>>> Matt >>>> On Mar 27, 2014 7:22 AM, "Matt Benson" <[email protected]> wrote: >>>> >>>>> Oh, well... It's no secret that ASM 3, being interface-based, is wholly >>>>> incompatible with ASM 4, which took the approach of using abstract classes >>>>> to significantly reduce the amount of code needed to accomplish a given >>>>> task. ASM 5 claims to be compatible with 4, which is why I, not realizing >>>>> that the plugins in question were based on ASM 3, suggested that simply >>>>> "dropping in" the new jar should suffice. The good news is that the >>>>> upgrade >>>>> process is not terribly onerous, if only someone steps to do it. >>>>> >>>>> Matt >>>>> On Mar 27, 2014 5:25 AM, "Mirko Friedenhagen" <[email protected]> >>>>> wrote: >>>>> >>>>>> Mark, >>>>>> >>>>>> the analyze goal depends on the >>>>>> org.apache.maven.shared:maven-dependency-analyzer:1.4 which depends on >>>>>> asm 3.3.1. The trunk already moved to 4.2. I will see what happens >>>>>> when switching to asm 5 :-) >>>>>> Regards Mirko >>>>>> -- >>>>>> http://illegalstateexception.blogspot.com/ >>>>>> https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) >>>>>> https://bitbucket.org/mfriedenhagen/ >>>>>> >>>>>> >>>>>> On Thu, Mar 27, 2014 at 5:45 AM, Mark Derricutt <[email protected]> wrote: >>>>>>> What version of the maven-dependency-plugin? I'm using 2.8 fine under >>>>>> JDK8 >>>>>>> and have been for some time - this is using the `copy-dependencies` >>>>>> goal and >>>>>>> nothing else tho... >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 27 Mar 2014, at 6:15, Steven Schlansker wrote: >>>>>>> >>>>>>>> Java 8 has now been out for a week and Maven is still not really >>>>>>>> compatible. >>>>>>>> In particular, the maven-shade-plugin and maven-dependency-plugin do >>>>>> not >>>>>>>> work >>>>>>>> due to an old version of ASM that throws >>>>>> ArrayIndexOutOfBoundsException on >>>>>>>> Java 8 class files. >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
