Re: More trouble with classpaths and velocity

2011-07-11 Thread Brett Porter
Any change you are picking up velocity-dep somewhere? That is commonly used, and as it has a different g/a ID it pops up alongside velocity at times. - Brett On 12/07/2011, at 1:59 AM, Benson Margulies wrote: > Nope, I'm giving m3 a wide berth while I'm working on plugins. > > On Mon, Jul 11,

Re: More trouble with classpaths and velocity

2011-07-11 Thread Benson Margulies
Nope, I'm giving m3 a wide berth while I'm working on plugins. On Mon, Jul 11, 2011 at 11:57 AM, Stephen Connolly wrote: > If you are running m3 then dependency:tree may be incorrect. > > On 11 July 2011 16:35, Benson Margulies wrote: >> Dependency:tree on my dev tree for the maven-jxr-plugin sh

Re: More trouble with classpaths and velocity

2011-07-11 Thread Stephen Connolly
If you are running m3 then dependency:tree may be incorrect. On 11 July 2011 16:35, Benson Margulies wrote: > Dependency:tree on my dev tree for the maven-jxr-plugin shows > precisely one copy of velocity 1.5: > org.apache.velocity:velocity:jar:1.5:compile. > > Any yet I'm stuck on the following

More trouble with classpaths and velocity

2011-07-11 Thread Benson Margulies
Dependency:tree on my dev tree for the maven-jxr-plugin shows precisely one copy of velocity 1.5: org.apache.velocity:velocity:jar:1.5:compile. Any yet I'm stuck on the following in the integration tests, which seems pretty strongly to indicate more than one copy in more than one classloader. Emb