Hi,
On 02.11.20 11:27, Nick Stolwijk wrote:
Hi folks,
We are struggling with our buildserver (Jenkins) and the Git-Flow Maven
Plugin[1] with regards to execute the Maven executable to run specific
goals and phases during release (i.e. run versions plugin to change version
or run `mvn verify` to check project).
In Jenkins you should run simple things like:
mvn clean verify
or if you deploy your artifacts to a repository manager:
mvn clean deploy
And check if your Jenkins uses the correct settings.xml (can be handled
via config-file-provider plugin in Jenkins).
If you like to make a release in Jenkins use a freestyle job to execute
that... via `mvn release:prepare release:perform`
I doubt that it would be a good idea to use git-flow-maven-plugin to
create a release ... Apart from that I think that git-flow is to complex
cause usually you don't need git flow with the complex branching model...
Kind regards
Karl Heinz Marbaise
The gitflow-m-p uses a flag to set the executable which needs to know if it
is on Linux (run mvn) or Windows (run mvn.cmd).
I was wondering what is the 'right' way to execute Maven from a plugin.
I've taken a look at the Maven Release Plugin and that one uses an internal
Executor framework. I have thought about Toolchain, but I didn't find an
example of a toolchain with Maven itself.
Can anyone enlighten me?
[1] https://github.com/aleksandr-m/gitflow-maven-plugin
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~
Lord Baden-Powell
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
