Karl Heinz Marbaise-3 wrote
>>I thought I could just enter it once as a plugin dependency in
>> the user project pom - assuming it would be the only one.
>
> You can give this via the plugin configuration and which means your
> plugin must resolve it's dependencies and make a required download fo
The users of my plugin define a dependency which the mojo unpacks and
extracts certain files from.
You know that such a plugin already exists? maven-dependency-plugin:unpack /
unpack-dependencies ?
https://maven.apache.org/plugins/maven-dependency-plugin/examples/unpacking-artifacts.html
Hi,
On 13/09/17 23:29, Adam Hardy wrote:
On 12/09/17 18:05, Adam Hardy wrote:
when I'm coding a mojo, if I call MavenProject's getArtifacts(), I
can only get artifacts from the project level dependencies.
How do I obtain artifacts from a plugin's dependencies?
The question which comes to
On 12/09/17 18:05, Adam Hardy wrote:
when I'm coding a mojo, if I call MavenProject's getArtifacts(), I can only
get artifacts from the project level dependencies.
How do I obtain artifacts from a plugin's dependencies?
The question which comes to my mind: Why do you need the dependencies o
Hi Adam,
On 12/09/17 18:05, Adam Hardy wrote:
Hi,
when I'm coding a mojo, if I call MavenProject's getArtifacts(), I can only get
artifacts from the project level dependencies.
How do I obtain artifacts from a plugin's dependencies?
The question which comes to my mind: Why do you need the
Hi,
when I'm coding a mojo, if I call MavenProject's getArtifacts(), I can only get
artifacts from the project level dependencies.
How do I obtain artifacts from a plugin's dependencies?
Presumably I call something like project.getPlugin(key).getDependencies()?
If the 'key' required for proje
