Never mind. Figured it out myself.
Tim Kettler schrieb:
Hi,
a plugin I'm writing depends on an artifact that is not part of the
projects dependencies nor should it be on the plugins classpath. So
defining it as a dependency under <project/> or <plugin> isn't an option.
I decided that the artifact is specified in the plugin configuration
like it is done in the dependency plugin for example. Looking at that
plugin's sources also showed how to create an Artifact instance from the
configuration data and how to resolve it. My problem now is that the
code in the dependency plugin doesn't resolve the artifacts transitive
dependencies.
Can anyone point me to some code that does this or provide a code snippet.
Thanks
-Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
