Maven 문제 - 지정한 목표는 프로젝트를 실행해야하지만이 디렉토리에는 POM이 없습니다.

Question

maven release plugin 2.2.1을 사용하고 있습니다. 내 경우에는 release:clean과 release:prepare이 성공적으로 실행됩니다. 그러나 release:perform을 실행하려고하면 다음 오류가 표시됩니다.

EXIMR-IM-187:rabbit_trunk manojkumarbardhan$ mvn release:perform 
[INFO] Scanning for projects... 
[INFO]                   
[INFO] ------------------------------------------------------------------------ 
[INFO] Building Curo Fabric Component for RabbitMQ 2.0.20-SNAPSHOT 
[INFO] ------------------------------------------------------------------------ 
[INFO] 
[INFO] --- maven-release-plugin:2.2.1:perform (default-cli) @ curo-fabric-component-rabbitmq-experiments --- 
[INFO] Checking out the project to perform the release ... 
[INFO] Executing: /bin/sh -c cd /Users/manojkumarbardhan/QURO_PROJECT/rabbit_trunk/target && svn --non-interactive checkout http://ssygh.dgxxxgdf.xxx.com:1080/SVNROOT/CURO/Experiments/migration/tags/curo-fabric-component-rabbitmq-experiments-2.0.19 /Users/manojkumarbardhan/QURO_PROJECT/rabbit_trunk/target/checkout 
[INFO] Working directory: /Users/manojkumarbardhan/QURO_PROJECT/rabbit_trunk/target 
[INFO] Executing goals 'deploy'... 
[WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance. 
[INFO] [INFO] Scanning for projects... 
[INFO] [INFO] ------------------------------------------------------------------------ 
[INFO] [INFO] BUILD FAILURE 
[INFO] [INFO] ------------------------------------------------------------------------ 
[INFO] [INFO] Total time: 0.115s 
[INFO] [INFO] Finished at: Thu Sep 05 17:40:01 GMT+05:30 2013 
[INFO] [INFO] Final Memory: 2M/81M 
[INFO] [INFO] ------------------------------------------------------------------------ 
[INFO] [ERROR] The goal you specified requires a project to execute but there is no POM in this directory (/Users/manojkumarbardhan/QURO_PROJECT/rabbit_trunk/target/checkout). Please verify you invoked Maven from the correct directory. -> [Help 1] 
[INFO] [ERROR] 
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. 
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging. 
[INFO] [ERROR] 
[INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles: 
[INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException 
[INFO] ------------------------------------------------------------------------ 
[INFO] BUILD FAILURE 
[INFO] ------------------------------------------------------------------------ 
[INFO] Total time: 10.528s 
[INFO] Finished at: Thu Sep 05 17:40:01 GMT+05:30 2013 
[INFO] Final Memory: 6M/81M 
[INFO] ------------------------------------------------------------------------ 
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.1:perform (default-cli) on project curo-fabric-component-rabbitmq-experiments: Maven execution failed, exit code: '1' -> [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/MojoExecutionException 

나는 무엇이 잘못되었는지 모른다.

나는 다음 오전 프로세스는 다음과 같습니다 -

1. 내 필요한 SVN은
2. 가 실행 mvn release:clean
3. 실행 명령을 실행
4. CD가 체크 아웃 디렉토리
5. 에 SVN에서 체크 아웃 mvn release:prepare
6. mvn release:perform을 실행하지만 실패합니다.

미리 감사드립니다.

Answer 1

개발자 연결에서 :

<scm> 
    <developerConnection>scm:svn:https://svn.mycompany.com/repos/myapplication/trunk/mycomponent/</developerConnection> 
</scm> 

는 해제하려는 Maven 프로젝트를 가리켜 야합니다.

<plugin> 
    <groupId>org.apache.maven.plugins</groupId> 
    <artifactId>maven-release-plugin</artifactId> 
    <version>2.5.2</version> 
    <configuration> 
    <tagBase>https://svn.mycompany.com/repos/myapplication/releases</tagBase> 
    </configuration> 
</plugin> 

하나는 (I도하지 않았다) 제대로 사용 페이지를 참조하는 모든 것이 잘 작동합니다 :

는 또한, 임의의 위치는 플러그인 구성에 릴리스 태그를 사용할 수 있습니다.

아직도 플러그인 로깅은 문제 (또는 가능한 문제)에 대한 정확한 정보를 제공해야한다고 생각합니다.