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
I knew one must exist, but I hadn't looked at the docs - interesting.
The reason why I wrote it myself was to try to avoid the duplication of
configuration items, to try to keep it succinct. Otherwise the user would have
to enter the desired file names twice (or more) - once to extract it, and again
to feed it into the next mojo where the file contents are used.
Furthermore the question is why do you need only certain files from it ?
It's a shared configuration file archive used by several projects. Not the
greatest idea, I know.
You can give this via the plugin configuration and which means your plugin
must resolve it's dependencies and make a required download for it...which can
be easily done by using a maven-artifact-transfer[3].
[3]:
https://maven.apache.org/shared/maven-artifact-transfer/install-project.html
Yes, true, but to try to keep it all succinct and intuitive, I figured it is
best to make it a real dependency from the XML point-of-view.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
