search

aleksandr-m / gitflow-maven-plugin

The Git-Flow Maven Plugin supports various Git workflows, including GitFlow and GitHub Flow. This plugin runs Git and Maven commands from the command line.
https://aleksandr-m.github.io/gitflow-maven-plugin/
Apache License 2.0
490 stars 182 forks source link

gitflow:release-finish gives a "Unknown lifecycle phase" error #278

Closed aish-kozhisherry closed 3 years ago

aish-kozhisherry commented 3 years ago

I have the gitlfow-maven-plugin defined in my pom.xml in the develop branch and ran mvn gitflow:release-start and the Build was successful with the release branch getting created as per the version I provided in the command line. Next in the release branch I ran mvn gitflow:release-finish and I invariably get the same error always (error below). I tried deleting my m2 repository and starting over again as well a couple of times, but no luck.

[ERROR] [ERROR] Unknown lifecycle phase "mx256m". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] [ERROR] org.apache.maven.lifecycle.LifecyclePhaseNotFoundException: Unknown lifecycle phase "mx256m". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. [ERROR] at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings (DefaultLifecycleExecutionPlanCalculator.java:248) [ERROR] at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions (DefaultLifecycleExecutionPlanCalculator.java:217) [ERROR] at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:126) [ERROR] at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:144) [ERROR] at org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan (BuilderCommon.java:97) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:111) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) [ERROR] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) [ERROR] at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) [ERROR] at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) [ERROR] at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) [ERROR] at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) [ERROR] at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) [ERROR] at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) [ERROR] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) [ERROR] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) [ERROR] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) [ERROR] at java.lang.reflect.Method.invoke (Method.java:566) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) [ERROR] [ERROR] [ERROR] [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

aish-kozhisherry commented 3 years ago

I had this tag in my pom.xml that caused this issue. Closing this issue now as removing that tag fixed the issue. <argLine>-Djava.security.egd=file:/dev/./urandom -Xmx256m</argLine>