On Jun 16, 2014, at 8:22 AM, Nigel Magnay <[email protected]> wrote:
> 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) > Then don't use Aether. Look at the technique used in the maven-dependency-tree if you want something that works in multiple versions of Maven. What happened with Aether is unfortunate but it's definitely a mess. > 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. Aside from a few outliers you should be fine with the version that Maven uses, if you want to use Aether directly. > > > 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 >> >> >> >> >> >> >> >> >> >> Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io --------------------------------------------------------- People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
