Plugin classpath issue

[Kevin Menard <km...@servprise.com>]

Hi,

I'm working on a plugin that I'd like to have invoked from the CLI, much 
like the jetty plugin.  I'm having difficulty in getting the classpath 
to work out the way I'd like though.  I have a dependency listed and can 
use classes from that dependency, but transitive dependencies don't seem 
to be working.  So, while I can use classes in my own dependency list, 
they can't use anything from their subsequent dependencies.  I've tried 
using @requiresDependencyResolution, but that didn't help.

Any advice would be much appreciated.

Thanks,
Kevin


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Plugin classpath issue

[Kristian Nordal <kr...@gmail.com>]

On 9/30/06, Kevin Menard <km...@servprise.com> wrote:
>
> Hi,
>
> I'm working on a plugin that I'd like to have invoked from the CLI, much
> like the jetty plugin.  I'm having difficulty in getting the classpath
> to work out the way I'd like though.  I have a dependency listed and can
> use classes from that dependency, but transitive dependencies don't seem
> to be working.  So, while I can use classes in my own dependency list,
> they can't use anything from their subsequent dependencies.  I've tried
> using @requiresDependencyResolution, but that didn't help.


Try using  "@requiresDependencyResolution runtime". Then ${project.artifacts}
should give you all the dependencies I believe.

--
Cheers,
Kristian