Hi, I have an issue I am not able to find an answer to.
How do I configure *dependency:unpack-dependencies* to process dependencies
declared inside the section?
There are three artifacts in this story: "product", "plugin" and
"compiler".
- "Plugin" depends on a "compiler" of a particular vers
Hello,
is there a way to specify dependencies for project when running this
plugin? I know there is a support for dependencies for plugin:
But I think this is not what I need. I am developing Seam archetype. I
want to have project without dependency on JBoss microcontainer.
But when
dependencies for plugin user
Thanks that works. I am now hoping to also be able to
include the actual
dependency classpath from the "user" project as well.
i.e. AndroMDA has a
base set of plugins. It will search the classpath for
others. I would like
it to be able to find any other AndroMDA pl
aven Users List'
Subject: RE: plugin dependencies for plugin user
Hi,
Maven.dependency.classpath only uses what is in the
project's descriptor,
however if you are just building an ant classpath you
can create the path
with your plugin's dependencies using
dependency.getPath.
rom cactus:
Cheers,
Brett
> -Original Message-
> From: J. Matthew Pryor [mailto:[EMAIL PROTECTED]
> Sent: Monday, 17 November 2003 11:14 AM
> To: [EMAIL PROTECTED]
> Subject: plugin dependencies for plugin user
>
>
> Hello,
&
Hello,
I am writing an AndroMDA (http://www.adnromda.org)
plugin for Maven and
basically have it working but I am having trouble
understanding
dependencies.
The AndroMDA pluging requires a bunch of jars to
compile (but mostly at
runtime). I have listed these in the dependencies
section of the pro
