how you make the release:perform working while it complains No sources to
compile
---------------------------------------------------------------------------------
Key: MRELEASE-349
URL: http://jira.codehaus.org/browse/MRELEASE-349
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: scm
Affects Versions: 2.0-beta-7
Environment: cvs and unix
Reporter: Michael Meng
I can not make the release:perform work at all, since it checked out the source
to one location and compile it on other location, which giving me the "No
sources to compile" error.
Does anyone have a detail log on how you make the release:perform to work on
cvs ?
The Working directory keep changing, any thing need to define in pom ?
The check out source location is:
/approot/cc/cruisecontrol-bin-2.7.1/checkout/projects/service/target/checkout
but it try to compile the source code on:
/approot/cc/cruisecontrol-bin-2.7.1/checkout/projects/service/target/checkout/target/checkout/
Thanks
[INFO] Executing: cvs -z3 -f -d :ext:[EMAIL PROTECTED]:/home/cvs_arch -q
checkout -r v88-01 -d checkout projects/service
[INFO] Working directory:
/approot/cc/cruisecontrol-bin-2.7.1/checkout/projects/service/target
[INFO] Executing goals 'deploy site-deploy'...
[INFO] Executing: mvn deploy site-deploy --no-plugin-updates
-DperformRelease=true -f pom.xml
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] [compiler:compile]
[INFO] No sources to compile
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Not compiling test sources
[INFO] [surefire:test]
[INFO] Tests are skipped.
[INFO] [jar:jar]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
