Ah, I'm using 0.9.0.M3, should I downgrade it ? Ideally I'd like to be able to support all versions of maven (this is actually being upgraded as things > maven 3.0.x aren't working)
It seems a bit messy that if I'm using aether in a module, and I want to use that module directly in a maven plugin, but I can see how the 'most normal' usecase would want it that way. I wonder if there's some classloader or uberjar/shading alternative. On Mon, Jun 16, 2014 at 1:09 PM, Jason van Zyl <[email protected]> wrote: > You are using Aether 1.0, stick with 0.9.0.M2. Maven itself hasn't > upgraded to 1.0. The version used in the core is exported for use in > plugins. > > On Jun 16, 2014, at 6:06 AM, Nigel Magnay <[email protected]> wrote: > > > Hi > > > > I have some pre-existing code that uses org.eclipse.aether, that works > fine. > > > > However, when I reference it and invoke it from a maven-plugin, I get > > > > A required class was missing while executing <plugin>: > > org.eclipse.aether.spi.connector.transport.TransporterFactory > > > > Looking at the urls spat out, it seems aether-spi is not of the > classpath. > > It's in the plugin manifest though. > > > > I assume it's being masked out somehow, as it's used in maven as well. I > > don't want to use Maven's RepositorySystem. > > > > What's one supposed to do in this circumstance? shade? > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > http://twitter.com/takari_io > --------------------------------------------------------- > > We know what we are, but know not what we may be. > > -- Shakespeare > > > > > > > > > >
