Stephen, Russel,
thanks for your suggestions so far. I will take a look into the plugins you
mentioned.
Our operations department is using puppet and I did some tiny steps with. I
agree it feels a bit like Maven because it is declarative as well. Now Ruby
is IMO Python's perlish brother, so I am
Hello there,
is there a way to switch to a different lifecycle depending on e.g. a
path/file etc? Or is the agreed way to just have another packaging?
Regards Mirko
--
Sent from my mobile
Hello,
I see that versions of plugins are either manageable in the pom or in the
lifecycle.
Now what about configurations of plugins? May these be hidden as well in an
extension/plugin?
I want to hide this because a lot of application developers look at our
company POM and shudder because of
On 6 July 2013 15:39, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
Hello there,
is there a way to switch to a different lifecycle depending on e.g. a
path/file etc? Or is the agreed way to just have another packaging?
The lifecycle for the pom comes from packaging.
The plugins that pom
Hello Barrie,
I know that :-) Our parent pom defines literally dozens of plugins,
configures them *and* adds a few profiles which change the configuration
and the plugins called on the existence of files, the environment (running
in Jenkins?) and I hoped I could split stuff a bit.
Regards Mirko
So what I am saying it that its only the packaging the defines which
lifecycle will be used.
You can't use files/paths.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
I think there are some little inconsistencies in vocabulary, causing wrong
analysis
there are 3 lifecycles: default, clean and site [1]
and packaging selects default plugin bindings for default lifecycle [2]
For the moment, I didn't dig sufficiently into everything to have every answers
and
default plugin version can effectively be injected
but that's *default* plugin versions
since actual lifecycle definitions are done in Maven core, you can't count on
it to upgrade version in your projects
in your case, where you want to define a new lifecycle, perhaps it will be
possible to
Hi,
The Mojo team is pleased to announce the release of the Mojo's Maven
Plugin for NSIS version 1.0-alpha-1.
This Maven Plugin enables Maven integration with the NSIS tools so that
Windows and Linux build machines can create Windows Installer EXEs.
