> On Apr 9, 2015, at 3:18 PM, Emmanuel Lecharny <[email protected]> wrote: > > Ok, bad news... One more reason to get rid with this dependency.
Well the good news is it was I who FUBARed the upgrade - not jgrapht. The artifact name changed and I did not change its reference in the core’s mvn test profiles. It’s fixed now. Can we cut a new release and try again? Thanks Shawn [email protected]
