Hi Jochen,
Yes, I just wanted to show you some code how to get the POM/model, and at
that point, you can do _whatever you want_ to it (this is how for example
nexus staging plugin "installs" itself btw). Still, you need to be very
careful _what_ you do here... is VERY easy to screw things up.
For
Hi, Tamas,
thanks for the link to the configuration-maven-plugin. If I do get
this right, you are essentially introducing a way to reuse
configuration snippets within the POM.
Which would of course be an interesting idea. I still wonder, whether
it isn't possible to find another plugin within my
Jochen,
for how it could work, take this example (demo plugin doing similar thing
you want):
https://github.com/cstamas/configuration-maven-plugin
That above if clearly "hacking" :)
As Herve said, no "proper" way to do it, except adding "standard" property
(like those mentioned by Herve) and sub
On Fri, Feb 3, 2017 at 10:27 AM, Hervé BOUTEMY wrote:
> b) is probably possible, but not recommended
A few words on how this would work, and *why* it is not recommended? I
am not interested in finding a solution for all Maven users, Just
something that works for me and my team.
Jochen
--
The
b) is probably possible, but not recommended
When we want to share some configuration between plugins, the usual solution is
to define a convention on a property name: see for example maven.test.skip that
is supported both by maven-compiler-plugin [1], Surefire [2], nar-maven-plugin
in multiple
Hi,
I'd like to create a plugin, which is intended to generate resources
for a web application.
In other words, the target directory would be the value, which is
typically configured as the webappDirectory property of the
maven-war-plugin.
To get that value, I see two options:
a) I create a pro
