Re: Use of code using aether in a plugin

2014-06-16 Thread Jason van Zyl
On Jun 16, 2014, at 8:22 AM, Nigel Magnay 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

Re: Use of code using aether in a plugin

2014-06-16 Thread Nigel Magnay
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,

Re: Use of code using aether in a plugin

2014-06-16 Thread Jason van Zyl
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 wrote: > Hi > > I have some pre-existing code that uses org.eclipse.aether, that works fine. > > However,

Use of code using aether in a plugin

2014-06-16 Thread Nigel Magnay
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 : org.eclipse.aether.spi.connector.transport.TransporterFactory Looking at the urls spat out, it se