"You don't have a SNAPSHOT project in the reactor projects list." when using Jenkins Maven release plugin

Dave

I'm using SVN, Maven 3.0.3 on the latest version of Jenkins and the Maven Release plugin. I'm trying to use the Maven release plugin (through Jenkins) do a dry run and so am executing the options …

Executing Maven:  -B -f /scratch/jenkins/workspace/myproject/myproject/pom.xml -DdevelopmentVersion=53.0.0-SNAPSHOT -DreleaseVersion=52.0.0 -Dusername=***** -Dpassword=********* -DskipTests -P prod -Dresume=false -DdryRun=true release:prepare

But the dry run is dying with the error below …

[JENKINS] Archiving /scratch/jenkins/workspace/myproject/myproject/pom.xml to /home/evotext/hudson_home/jobs/myproject/modules/org.mainco.subco$myproject/builds/2013-11-18_16-09-14/archive/org.mainco.subco/myproject/52.0.0/myproject-52.0.0.pom
Waiting for Jenkins to finish collecting data
mavenExecutionResult exceptions not empty
message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project myproject: You don't have a SNAPSHOT project in the reactor projects list.
cause : You don't have a SNAPSHOT project in the reactor projects list.
    Stack trace : 
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal  org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project myproject: You don't have a SNAPSHOT project in the reactor projects list.
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
    at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:117)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
    at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:178)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at hudson.maven.Maven3Builder.call(Maven3Builder.java:129)
    at hudson.maven.Maven3Builder.call(Maven3Builder.java:67)
    at hudson.remoting.UserRequest.perform(UserRequest.java:118)
    at hudson.remoting.UserRequest.perform(UserRequest.java:48)
    at hudson.remoting.Request$2.run(Request.java:326)
    at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:744)
Caused by: org.apache.maven.plugin.MojoFailureException: You don't have a SNAPSHOT project in the reactor projects list.
    at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:219)
    at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
    ... 30 more
Caused by: org.apache.maven.shared.release.ReleaseFailureException: You don't have a SNAPSHOT project in the reactor projects list.
    at org.apache.maven.shared.release.phase.CheckPomPhase.execute(CheckPomPhase.java:111)
    at org.apache.maven.shared.release.phase.CheckPomPhase.simulate(CheckPomPhase.java:123)
    at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:199)
    at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140)
    at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103)
    at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211)
    ... 33 more

My SVN checkout method is set to "Always checkout a fresh copy" and I have a snapshot version in question in my snapshot repository, but not in my release repository. Is there a way I can get the "reactor projects list" to look at my snapshot repo?

Edit: I'm including the snippet of my pom where the project gets its version -- it inherits it from a parent

    <parent>
            <artifactId>subco</artifactId>
            <groupId>org.mainco.subco</groupId>
            <version>52.0.0</version>
    </parent>
Daniel Kaplan

You're trying to release an artifact that's not a snapshot. That means your artifact's version number is something like 3.0.3. That version number implies its already been released. You can't release a release. There would be no changes in between and therefore no point.

You're only supposed to release SNAPSHOT versions. That means your version number would be like 3.0.3-SNAPSHOT.

本文收集自互联网,转载请注明来源。

如有侵权,请联系[email protected] 删除。

编辑于
0

我来说两句

0条评论
登录后参与评论

相关文章

来自分类Dev

Jenkins管道中使用Maven Release Plugin

来自分类Dev

在pom中使用的Jenkins Maven-release-plugin -D属性

来自分类Dev

在Jenkins中将Maven-release-plugin与完整性(MKS)一起用作源代码管理

来自分类Dev

创建Maven-release-plugin标签

来自分类Dev

Maven Release Build Skip测试用例失败-Jenkins

来自分类Dev

Maven Release Build Skip测试用例失败-Jenkins

来自分类Dev

maven-release-plugin将快照部署到archiva

来自分类Dev

Maven-release-plugin在提交之前自动运行脚本

来自分类Dev

在git-1.8.5中使用Maven-release-plugin

来自分类Dev

将Maven-release-plugin添加到Android Studio

来自分类Dev

如何阻止 maven-release-plugin 使用旧版本的 maven-gpg-plugin

来自分类Dev

耳朵不是使用maven-ear-plugin在Jenkins上构建的

来自分类Dev

耳朵不是使用Maven-ear-plugin在Jenkins上构建的

来自分类Dev

在执行Maven-release-plugin的目标期间如何关闭配置文件

来自分类Dev

多模块项目中的maven-release-plugin,每个模块都有单独的git存储库

来自分类Dev

maven-release-plugin不使用作业配置或/和.ssh / config中提供的ssh密钥

来自分类Dev

在GitHub上使用maven-release-plugin“您不能推送到git://github.com / ...”

来自分类Dev

Maven-surefire-plugin在SpringBoot 2.2.2.RELEASE及更高版本中不起作用

来自分类Dev

为什么maven-release-plugin上传构建信息?可以将其删除吗?

来自分类Dev

在GitHub上使用maven-release-plugin“您不能推送到git://github.com / ...”

来自分类Dev

maven-release-plugin:2.5:prepare失败,并显示“写入POM时出错:(访问被拒绝)”

来自分类Dev

How to pass default values to a Jenkins build using the Parameterized Build Plugin?

来自分类Dev

当我使用maven-release-plugin释放分支时,为什么它尝试从修订版0创建分支?

来自分类Dev

在插件org.springframework.boot:spring-boot-maven-plugin:1.1.4.RELEASE中找不到目标''

来自分类Dev

在插件org.springframework.boot:spring-boot-maven-plugin:1.1.4.RELEASE中找不到目标''

来自分类Dev

Mercurial Plugin, Jenkins and Cloudbees

来自分类Dev

Jenkins无法识别Maven

来自分类Dev

Jenkins Artifactory插件与Maven

来自分类Dev

Eclipse maven run configuration using 'run' goal from tomcat7 maven plugin doesn't respect default context path

Related 相关文章

  1. 1

    Jenkins管道中使用Maven Release Plugin

  2. 2

    在pom中使用的Jenkins Maven-release-plugin -D属性

  3. 3

    在Jenkins中将Maven-release-plugin与完整性(MKS)一起用作源代码管理

  4. 4

    创建Maven-release-plugin标签

  5. 5

    Maven Release Build Skip测试用例失败-Jenkins

  6. 6

    Maven Release Build Skip测试用例失败-Jenkins

  7. 7

    maven-release-plugin将快照部署到archiva

  8. 8

    Maven-release-plugin在提交之前自动运行脚本

  9. 9

    在git-1.8.5中使用Maven-release-plugin

  10. 10

    将Maven-release-plugin添加到Android Studio

  11. 11

    如何阻止 maven-release-plugin 使用旧版本的 maven-gpg-plugin

  12. 12

    耳朵不是使用maven-ear-plugin在Jenkins上构建的

  13. 13

    耳朵不是使用Maven-ear-plugin在Jenkins上构建的

  14. 14

    在执行Maven-release-plugin的目标期间如何关闭配置文件

  15. 15

    多模块项目中的maven-release-plugin,每个模块都有单独的git存储库

  16. 16

    maven-release-plugin不使用作业配置或/和.ssh / config中提供的ssh密钥

  17. 17

    在GitHub上使用maven-release-plugin“您不能推送到git://github.com / ...”

  18. 18

    Maven-surefire-plugin在SpringBoot 2.2.2.RELEASE及更高版本中不起作用

  19. 19

    为什么maven-release-plugin上传构建信息?可以将其删除吗?

  20. 20

    在GitHub上使用maven-release-plugin“您不能推送到git://github.com / ...”

  21. 21

    maven-release-plugin:2.5:prepare失败,并显示“写入POM时出错:(访问被拒绝)”

  22. 22

    How to pass default values to a Jenkins build using the Parameterized Build Plugin?

  23. 23

    当我使用maven-release-plugin释放分支时,为什么它尝试从修订版0创建分支?

  24. 24

    在插件org.springframework.boot:spring-boot-maven-plugin:1.1.4.RELEASE中找不到目标''

  25. 25

    在插件org.springframework.boot:spring-boot-maven-plugin:1.1.4.RELEASE中找不到目标''

  26. 26

    Mercurial Plugin, Jenkins and Cloudbees

  27. 27

    Jenkins无法识别Maven

  28. 28

    Jenkins Artifactory插件与Maven

  29. 29

    Eclipse maven run configuration using 'run' goal from tomcat7 maven plugin doesn't respect default context path

热门标签

归档