I was wrong about the property value, it's cvs_native instead of cvsexe
mvn release:prepare -Dmaven.scm.provider.cvs.implementation=cvs_native
Emmanuel Venisse a écrit :
oops typo error. we can't check the registry.
Emmanuel Venisse a écrit :
We can check the registry, it isn't possible with java without JNI,
but you can use the system cvs.
You just need to use the maven.scm.provider.cvs.implementation property
mvn release:prepare -Dmaven.scm.provider.cvs.implementation=cvsexe
I think I'll add a parameter later in release plugin so you'll can
define it in your pom
Emmanuel
Antonio Parolini a écrit :
Hello again,
I found the problem: It's windows related:
The new beta-5 shapshot release is not using the system CVS (cvsnt
for me)
anymore, but a build-in java cvs client ( from netbeans, as the stack
trace
shows). The problem is that CVS NT stores the cvs login info into the
registry and not into -cvspass!
It would be nice if the build-in client could check the registry too!
-toni
Antonio Parolini wrote:
Hello,
We are using the mave-release-plugin 2.0-beta-5-SNAPSHOT, since it
corrects a lot of bug we had in beta 4.
But since a few days, it dosen-t seems to connect to our CVS repo. My
pom is ok, cause when I switch to beta-4, it succed to connect.
Moreover,
when using the SCM plugin, it connect allright.
Here is the stack:
[INFO] [release:prepare]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: cvs -z3 -f -d
:pserver:[EMAIL PROTECTED]:/local/cvs/reps/Framework_Jade -n -q update -d
[INFO] Working directory: D:\workspace\prjStd2_Jboss-parent
[ERROR] Didn't find password for CVSROOT
':pserver:[EMAIL PROTECTED]:/local/cvs/reps/Framework_Jade'.
org.netbeans.lib.cvsclient.connection.AuthenticationException: Wrong
Password.
at
org.netbeans.lib.cvsclient.connection.PServerConnection.openConnection(PServerConnection.java:231)
at
org.netbeans.lib.cvsclient.connection.PServerConnection.open(PServerConnection.java:326)
I tried a -Dpassword=xxx when running maven, also doing a cvs
login, but
still no luck.
Is this a new bug in the maven-release-plugin ?
Thanks in advance.
-toni
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
