That’s a big question :)
My problem was that I wasn’t sure what the parameters meant, and what the
settings meant, and most especially, what the properties available in the build
are. It’s a general problem with technical docs: when you develop a feature and
want to describe it, it is hard to
Counter question: where should we improve the documentation?
On Thu, 08 Nov 2018 19:02:03 +0100, Russell Gold
wrote:
Thanks, that was the problem :)
On Nov 7, 2018, at 3:48 PM, Robert Scholte wrote:
Did you specify the requiresDependencyResolution of the @Mojo?
Robert
[1]
Thanks, that was the problem :)
> On Nov 7, 2018, at 3:48 PM, Robert Scholte wrote:
>
> Did you specify the requiresDependencyResolution of the @Mojo?
>
> Robert
>
> [1]
> https://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/index.html#Supported_Annotations
> On Tue, 06 Nov
Did you specify the requiresDependencyResolution of the @Mojo?
Robert
[1]
https://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/index.html#Supported_Annotations
On Tue, 06 Nov 2018 21:24:03 +0100, Russell Gold
wrote:
I am writing a plugin which does post-processing on some
I am writing a plugin which does post-processing on some classes compiled in
the build, so I have defined a parameter that I would like Maven to fill in
with the appropriate list of dependencies, but I am clearly misunderstanding
how to do that. Here is what I have:
>
