Bug#865499: gradle fails to start in unstable after plexus-containers update

2017-11-18 Thread Dillon Gilmore
I'm actually having the inverse issue. Unsure of what changes have been made since this last report: Caused by: java.lang.IllegalArgumentException: Cannot find JAR 'plexus-component-annotations.jar' required by module 'gradle-dependency-management' using classpath or distribution directory

Bug#865499: gradle fails to start in unstable after plexus-containers update

2017-06-23 Thread Emmanuel Bourg
Le 22/06/2017 à 06:01, tony mancill a écrit : > I'm not yet sure whether the problem lies with gradle or > plexus-containers, but perhaps we should reassign this bug to > plexus-containers1.5 (or create a new one) to temporarily prevent the > migration. I'm opening the bug against gradle in case

Bug#865499: gradle fails to start in unstable after plexus-containers update

2017-06-21 Thread tony mancill
Package: gradle Version: 3.2.1-1 Severity: important Hi, It looks like the recent upload of plexus-containers1.5 [1] has left gradle in a bad way in unstable (and possibly soon in testing too). It fails to start, and running "gradle --stacktrace" results in a long stacktrace that includes this: