On 5/26/05, Julian Wood <[EMAIL PROTECTED]> wrote: > And the source Xref points to a 1.5-beta-4-SNAPSHOT, which is not > available for download anywhere (that I can find), and which of course > doesn't correspond to the stack trace I have. > > Wasn't maven created in the first place to avoid exactly these kinds of > problems? What am I missing here?
My mistake. I've held the code on a branch for way too long, and didn't update the descriptor when publishing the site. http://svn.apache.org/repos/asf/maven/maven-1/plugins/branches/scm-1.5-branch I'll be trying to merge that back to trunk today. You are correct, the SCM plugin is becoming a thin wrapper around the maven-scm project. If you can try that: http://svn.apache.org/repos/asf/maven/scm/trunk It m ay give more insight into what is happening. Maven SCM requires Maven 2.0 alpha-2 to build. Run m2 install at the root (it will build all of the providers, if any fail, you can skip straight to the cvs one since all the prerequesites will have been built). I was just replying to your other email. Can I confirm: - are you on Mac OS X? - what is the CVS client version there? - do you have access to a different machine to try this on? (trying to figure if it is your env, or your project that exhibits the bug) Thanks, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
