Closed toschneck closed 6 years ago
use this config for all projects: profile:
<profile>
<id>jenkins</id>
<properties>
<maven.settings.hook>-s ${user.home}/mvn_settings/sakuli-settings.xml</maven.settings.hook>
<performRelease>true</performRelease>
</properties>
</profile>
plugin config:
<plugin>
<groupId>com.amashchenko.maven.plugin</groupId>
<artifactId>gitflow-maven-plugin</artifactId>
<configuration>
<verbose>true</verbose>
<keepBranch>false</keepBranch>
<fetchRemote>true</fetchRemote>
<pushRemote>true</pushRemote>
<postReleaseGoals>deploy</postReleaseGoals>
<postHotfixGoals>deploy</postHotfixGoals>
<!--load maven settings.xml for sub-processes of maven-->
<argLine>-DperformRelease=${performRelease} ${maven.settings.hook}</argLine>
<gitFlowConfig>
<!-- default git flow prefixes -->
<productionBranch>master</productionBranch>
<developmentBranch>dev</developmentBranch>
<featureBranchPrefix>feature/</featureBranchPrefix>
<releaseBranchPrefix>release/</releaseBranchPrefix>
<hotfixBranchPrefix>hotfix/</hotfixBranchPrefix>
<!-- non default 'v' prefix -->
<versionTagPrefix>v</versionTagPrefix>
</gitFlowConfig>
<commitMessages>
<!--suppress MavenModelInspection -->
<featureStartMessage>create feature-branch '@{featureName}' - update version to v@{version}
</featureStartMessage>
<!--suppress MavenModelInspection -->
<featureFinishMessage>merge feature-branch '@{featureName}' - update version to v@{version}
</featureFinishMessage>
<hotfixStartMessage>update version for hotfix to v@{version}</hotfixStartMessage>
<hotfixFinishMessage>update for next development version to v@{version}</hotfixFinishMessage>
<releaseStartMessage>update version for release to v@{version}</releaseStartMessage>
<releaseFinishMessage>update for next development version to v@{version}</releaseFinishMessage>
</commitMessages>
</configuration>
</plugin>
Due to outdated jgitflow lib the latest jgitflow-maven-plugin won't work any more, see also MJF-301 1.0-m5.1 - is not working anymore using SSH (git://) after Github.com crypto update
TODO: