Hi All,
I'm currently exploring using the scm plugin, primarily interested in using
it in conjunction with the release plugin. Having a bit of a problem
though... and help appreciated.
I think I can see what's happening to cause the first issue but don't know
how to fix it. My particular maven environment is cygwin+wincvs using
'local' access method. Know it's not the most popular access method but am
obliged to use it for historic reasons.
It appears to me that during the 'release' phase the project in question
isn't being checked out properly and as a result mvn is choking as it can't
find the pom.xml (or anything else!). I believe this is due to a leading
slash being passed to WinCVS somewhere.
If I remove the leading slash in the CVS/Repository file a CVS update will
correctly pull the files in. (In fact can see the slash in the command
that's being executed).
The scm section in my pom contains....
<scm>
<connection>
scm|cvs|local|s:/statarb/Modules/gsa/cvsroot|
</connection>
</scm>
[EMAIL PROTECTED] ~/eclipse_workspace/gsagrid
$ mvn release:perform
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO]
----------------------------------------------------------------------------
[INFO] Building Unnamed - gsa:gsagrid:jar:1.3-SNAPSHOT
[INFO] task-segment: [release:perform] (aggregator-style)
[INFO]
----------------------------------------------------------------------------
[INFO] [release:perform]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: cvs -z3 -f -d s:/statarb/Modules/gsa/cvsroot -q checkout
-r mvngrid1_2 -d checkout /gsagrid
[INFO] Working directory: C:\smitar\eclipse_workspace\gsagrid\target
[INFO] Executing: mvn deploy --no-plugin-updates -DperformRelease=true
[INFO] Scanning for projects...
[INFO]
----------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [deploy]
[INFO]
----------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Cannot execute mojo: resources. It requires a project with an
existing pom.xml, but the build is not using one.
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Fri Jun 16 17:56:16 BST 2006
[INFO] Final Memory: 3M/7M
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error executing Maven: Maven execution failed, exit code: '1'
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 5 seconds
[INFO] Finished at: Fri Jun 16 17:56:16 BST 2006
[INFO] Final Memory: 4M/8M
[INFO]
------------------------------------------------------------------------
$ cd target/checkout/
[EMAIL PROTECTED] ~/eclipse_workspace/gsagrid/target/checkout
$ ls -l
total 0
drwx------+ 2 asmith_gsa mkgroup-l-d 0 Jun 16 17:56 CVS
[ i.e. empty directory - nothing has been checked out ]
[EMAIL PROTECTED] ~/eclipse_workspace/gsagrid/target/checkout
$ cat CVS/Repository
/gsagrid
[EMAIL PROTECTED] ~/eclipse_workspace/gsagrid/target/checkout
$ echo 'gsagrid' > CVS/Repository
[EMAIL PROTECTED] ~/eclipse_workspace/gsagrid/target/checkout
$ cvs update
cvs update: Updating .
U .cvsignore
U build.xml
U gsagrid.iml
U manifest.mf
U pom.xml
etc. etc.
[ i.e. modifying the Repository element fixes CVS and the checkout succeeds
]
