You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Dennis Lundberg <de...@mdh.se> on 2006/01/08 23:54:49 UTC
[m1] maven-scm-plugin-1.6-SNAPSHOT Error running scm:status ans scm:prepare-release
Hi all
I'm beginning to get grey hairs now...
I just finished the patch for MPSCM-67 which solved a problem I had.
When developing the patch I was working off the "maven-scm-plugin-1.5"
tag, then ported the patch to trunk. Now I can't get trunk to work, at
all. With or without my patch.
Environment: CVSNT and Windows XP.
maven scm:status returns:
BUILD FAILED
File...... C:\Documents and
Settings\dlg01\.maven\cache\maven-scm-plugin-1.6-SNAPSHOT\plugin.jelly
Element... scm:status
Line...... 215
Column.... 42
Exception while executing SCM command.
maven scm:prepare-release returns:
BUILD FAILED
File...... C:\Documents and
Settings\dlg01\.maven\cache\maven-scm-plugin-1.6-SNAPSHOT\plugin.jelly
Element... scm:status
Line...... 263
Column.... 158
Exception while executing SCM command.
Both these places are calls to the ScmStatusBean.
Running with -X gets me a nice stacktrace:
Caused by: org.apache.maven.scm.ScmException: Exception while executing
SCM command.
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
at
org.apache.maven.scm.provider.cvslib.CvsScmProvider.login(CvsScmProvider.java:506)
at
org.apache.maven.scm.provider.AbstractScmProvider.login(AbstractScmProvider.java:204)
at
org.apache.maven.scm.provider.AbstractScmProvider.status(AbstractScmProvider.java:247)
at
org.apache.maven.plugins.scm.ScmStatusBean.status(ScmStatusBean.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:230)
... 16 more
Caused by: org.apache.maven.scm.ScmException: password is required
at
org.apache.maven.scm.provider.cvslib.command.login.CvsPass.execute(CvsPass.java:127)
at
org.apache.maven.scm.provider.cvslib.command.login.CvsLoginCommand.executeLoginCommand(CvsLoginCommand.java:57)
at
org.apache.maven.scm.login.AbstractLoginCommand.executeCommand(AbstractLoginCommand.java:44)
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55)
... 25 more
This seems to imply that there is no password. So I modified
plugin.jelly a bit and confirmed that the correct password is indeed
sent to the ScmStatusBean. But the call to the scm provider fails.
I've tried to diff what else has happened since 1.5 was released, but
can't find anything. The only thing that stands out is the upgrade of
maven-scm from 1.0-alpha-1 to 1.0-alpha-2.
Does anyone have a clue to what's going wrong?
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] maven-scm-plugin-1.6-SNAPSHOT Error running scm:status ans
scm:prepare-release
Posted by Dennis Lundberg <de...@apache.org>.
Lukas,
The thing is that I don't use anonymous pserver, I use username and
password.
--
Dennis Lundberg
Lukas Theussl wrote:
> Dennis,
>
> A hint from Emmanuel has led me to the solution of this problem: for
> anonymous (pserver) access you have to insert a delimiter (:) between
> the user name and the @, to indicate that there is a password but it is
> empty. It's documented on the bottom of this page:
> http://maven.apache.org/scm/cvs.html (and then people say Maven is badly
> documented ... you just have to find it! ;)).
>
> Anyway, scm:checkout and scm:status work now for me (even though
> scm:status still doesn't give me any output).
>
> Cheers,
> Lukas
>
>
> Dennis Lundberg wrote:
>
>> Hi Lukas
>>
>> MPSCM-67 is a different matter. The new patch for that issue was
>> uploaded because the first patch used absolute paths (in the svn diff
>> itself, not in maven code). That issue is solved by the patch there.
>>
>> This problem, on the other hand, I haven't solved yet. I figured that
>> I would use the latest snapshot of maven-scm and give it a try, but
>> I'm having trouble building it because of problems with the test
>> cases, see SCM-121.
>>
>> I'll have another go at it this week, using maven-scm 1.0-beta-2.
>>
>> Are you able to run "maven scm:status" with the latest
>> maven-scm-plugin-1.6-SNAPSHOT on a project that uses cvs as scm? If so
>> can you send me some specifics about your environment.
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] maven-scm-plugin-1.6-SNAPSHOT Error running scm:status ans
scm:prepare-release
Posted by Lukas Theussl <lt...@apache.org>.
Dennis,
A hint from Emmanuel has led me to the solution of this problem: for
anonymous (pserver) access you have to insert a delimiter (:) between
the user name and the @, to indicate that there is a password but it is
empty. It's documented on the bottom of this page:
http://maven.apache.org/scm/cvs.html (and then people say Maven is badly
documented ... you just have to find it! ;)).
Anyway, scm:checkout and scm:status work now for me (even though
scm:status still doesn't give me any output).
Cheers,
Lukas
Dennis Lundberg wrote:
> Hi Lukas
>
> MPSCM-67 is a different matter. The new patch for that issue was
> uploaded because the first patch used absolute paths (in the svn diff
> itself, not in maven code). That issue is solved by the patch there.
>
> This problem, on the other hand, I haven't solved yet. I figured that
> I would use the latest snapshot of maven-scm and give it a try, but
> I'm having trouble building it because of problems with the test
> cases, see SCM-121.
>
> I'll have another go at it this week, using maven-scm 1.0-beta-2.
>
> Are you able to run "maven scm:status" with the latest
> maven-scm-plugin-1.6-SNAPSHOT on a project that uses cvs as scm? If so
> can you send me some specifics about your environment.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] maven-scm-plugin-1.6-SNAPSHOT Error running scm:status ans
scm:prepare-release
Posted by Lukas Theussl <lt...@apache.org>.
>
> When you say "anonymous" and "developer", could those be "pserver" and
> "ext" instead?
>
Yes, that's what I meant.
-Lukas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] maven-scm-plugin-1.6-SNAPSHOT Error running scm:status ans
scm:prepare-release
Posted by Dennis Lundberg <de...@mdh.se>.
Interesting!
This helps narrow down where to look. I'm now convinced that the problem
lies in maven-scm. I found a couple of issues in there but have not
found the solution for this one yet.
When you say "anonymous" and "developer", could those be "pserver" and
"ext" instead?
--
Dennis Lundberg
Lukas Theussl wrote:
> Dennis,
>
> I'm on Linux, latest snapshot plugins from svn and maven-scm 1.0-beta-2.
>
> In short: I can reproduce the problem, 'maven scm:status' gives me the
> same error that you got (password is required). When I do a 'cvs login'
> manually before, the build succeeds, but I don't get any output.
>
> One thing I noted: this only happens with anonymous access, with
> developer access the build always succeeds (without output).
>
> HTH,
> Lukas
>
>
>
> Dennis Lundberg wrote:
>> Hi Lukas
>>
>> MPSCM-67 is a different matter. The new patch for that issue was
>> uploaded because the first patch used absolute paths (in the svn diff
>> itself, not in maven code). That issue is solved by the patch there.
>>
>> This problem, on the other hand, I haven't solved yet. I figured that
>> I would use the latest snapshot of maven-scm and give it a try, but
>> I'm having trouble building it because of problems with the test
>> cases, see SCM-121.
>>
>> I'll have another go at it this week, using maven-scm 1.0-beta-2.
>>
>> Are you able to run "maven scm:status" with the latest
>> maven-scm-plugin-1.6-SNAPSHOT on a project that uses cvs as scm? If so
>> can you send me some specifics about your environment.
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] maven-scm-plugin-1.6-SNAPSHOT Error running scm:status ans
scm:prepare-release
Posted by Lukas Theussl <lt...@apache.org>.
Dennis,
I'm on Linux, latest snapshot plugins from svn and maven-scm 1.0-beta-2.
In short: I can reproduce the problem, 'maven scm:status' gives me the
same error that you got (password is required). When I do a 'cvs login'
manually before, the build succeeds, but I don't get any output.
One thing I noted: this only happens with anonymous access, with
developer access the build always succeeds (without output).
HTH,
Lukas
Dennis Lundberg wrote:
> Hi Lukas
>
> MPSCM-67 is a different matter. The new patch for that issue was
> uploaded because the first patch used absolute paths (in the svn diff
> itself, not in maven code). That issue is solved by the patch there.
>
> This problem, on the other hand, I haven't solved yet. I figured that I
> would use the latest snapshot of maven-scm and give it a try, but I'm
> having trouble building it because of problems with the test cases, see
> SCM-121.
>
> I'll have another go at it this week, using maven-scm 1.0-beta-2.
>
> Are you able to run "maven scm:status" with the latest
> maven-scm-plugin-1.6-SNAPSHOT on a project that uses cvs as scm? If so
> can you send me some specifics about your environment.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] maven-scm-plugin-1.6-SNAPSHOT Error running scm:status ans
scm:prepare-release
Posted by Dennis Lundberg <de...@mdh.se>.
Hi Lukas
MPSCM-67 is a different matter. The new patch for that issue was
uploaded because the first patch used absolute paths (in the svn diff
itself, not in maven code). That issue is solved by the patch there.
This problem, on the other hand, I haven't solved yet. I figured that I
would use the latest snapshot of maven-scm and give it a try, but I'm
having trouble building it because of problems with the test cases, see
SCM-121.
I'll have another go at it this week, using maven-scm 1.0-beta-2.
Are you able to run "maven scm:status" with the latest
maven-scm-plugin-1.6-SNAPSHOT on a project that uses cvs as scm? If so
can you send me some specifics about your environment.
--
Dennis Lundberg
Lukas Theussl wrote:
> Dennis,
>
> Have you figured out what was going on here? Does the second patch that
> you attached to MPSCM-67 fix this?
>
> Cheers,
> Lukas
>
>
> Dennis Lundberg wrote:
>> Hi all
>>
>> I'm beginning to get grey hairs now...
>>
>> I just finished the patch for MPSCM-67 which solved a problem I had.
>> When developing the patch I was working off the "maven-scm-plugin-1.5"
>> tag, then ported the patch to trunk. Now I can't get trunk to work, at
>> all. With or without my patch.
>>
>> Environment: CVSNT and Windows XP.
>>
>>
>> maven scm:status returns:
>>
>> BUILD FAILED
>> File...... C:\Documents and
>> Settings\dlg01\.maven\cache\maven-scm-plugin-1.6-SNAPSHOT\plugin.jelly
>> Element... scm:status
>> Line...... 215
>> Column.... 42
>> Exception while executing SCM command.
>>
>>
>> maven scm:prepare-release returns:
>>
>> BUILD FAILED
>> File...... C:\Documents and
>> Settings\dlg01\.maven\cache\maven-scm-plugin-1.6-SNAPSHOT\plugin.jelly
>> Element... scm:status
>> Line...... 263
>> Column.... 158
>> Exception while executing SCM command.
>>
>> Both these places are calls to the ScmStatusBean.
>>
>>
>> Running with -X gets me a nice stacktrace:
>>
>> Caused by: org.apache.maven.scm.ScmException: Exception while
>> executing SCM command.
>> at
>> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
>>
>> at
>> org.apache.maven.scm.provider.cvslib.CvsScmProvider.login(CvsScmProvider.java:506)
>>
>> at
>> org.apache.maven.scm.provider.AbstractScmProvider.login(AbstractScmProvider.java:204)
>>
>> at
>> org.apache.maven.scm.provider.AbstractScmProvider.status(AbstractScmProvider.java:247)
>>
>> at
>> org.apache.maven.plugins.scm.ScmStatusBean.status(ScmStatusBean.java:48)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:324)
>> at
>> org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:230)
>>
>> ... 16 more
>> Caused by: org.apache.maven.scm.ScmException: password is required
>> at
>> org.apache.maven.scm.provider.cvslib.command.login.CvsPass.execute(CvsPass.java:127)
>>
>> at
>> org.apache.maven.scm.provider.cvslib.command.login.CvsLoginCommand.executeLoginCommand(CvsLoginCommand.java:57)
>>
>> at
>> org.apache.maven.scm.login.AbstractLoginCommand.executeCommand(AbstractLoginCommand.java:44)
>>
>> at
>> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55)
>>
>> ... 25 more
>>
>>
>> This seems to imply that there is no password. So I modified
>> plugin.jelly a bit and confirmed that the correct password is indeed
>> sent to the ScmStatusBean. But the call to the scm provider fails.
>>
>> I've tried to diff what else has happened since 1.5 was released, but
>> can't find anything. The only thing that stands out is the upgrade of
>> maven-scm from 1.0-alpha-1 to 1.0-alpha-2.
>>
>> Does anyone have a clue to what's going wrong?
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] maven-scm-plugin-1.6-SNAPSHOT Error running scm:status ans
scm:prepare-release
Posted by Lukas Theussl <lt...@apache.org>.
Dennis,
Have you figured out what was going on here? Does the second patch that
you attached to MPSCM-67 fix this?
Cheers,
Lukas
Dennis Lundberg wrote:
> Hi all
>
> I'm beginning to get grey hairs now...
>
> I just finished the patch for MPSCM-67 which solved a problem I had.
> When developing the patch I was working off the "maven-scm-plugin-1.5"
> tag, then ported the patch to trunk. Now I can't get trunk to work, at
> all. With or without my patch.
>
> Environment: CVSNT and Windows XP.
>
>
> maven scm:status returns:
>
> BUILD FAILED
> File...... C:\Documents and
> Settings\dlg01\.maven\cache\maven-scm-plugin-1.6-SNAPSHOT\plugin.jelly
> Element... scm:status
> Line...... 215
> Column.... 42
> Exception while executing SCM command.
>
>
> maven scm:prepare-release returns:
>
> BUILD FAILED
> File...... C:\Documents and
> Settings\dlg01\.maven\cache\maven-scm-plugin-1.6-SNAPSHOT\plugin.jelly
> Element... scm:status
> Line...... 263
> Column.... 158
> Exception while executing SCM command.
>
> Both these places are calls to the ScmStatusBean.
>
>
> Running with -X gets me a nice stacktrace:
>
> Caused by: org.apache.maven.scm.ScmException: Exception while executing
> SCM command.
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
>
> at
> org.apache.maven.scm.provider.cvslib.CvsScmProvider.login(CvsScmProvider.java:506)
>
> at
> org.apache.maven.scm.provider.AbstractScmProvider.login(AbstractScmProvider.java:204)
>
> at
> org.apache.maven.scm.provider.AbstractScmProvider.status(AbstractScmProvider.java:247)
>
> at
> org.apache.maven.plugins.scm.ScmStatusBean.status(ScmStatusBean.java:48)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:230)
> ... 16 more
> Caused by: org.apache.maven.scm.ScmException: password is required
> at
> org.apache.maven.scm.provider.cvslib.command.login.CvsPass.execute(CvsPass.java:127)
>
> at
> org.apache.maven.scm.provider.cvslib.command.login.CvsLoginCommand.executeLoginCommand(CvsLoginCommand.java:57)
>
> at
> org.apache.maven.scm.login.AbstractLoginCommand.executeCommand(AbstractLoginCommand.java:44)
>
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55)
>
> ... 25 more
>
>
> This seems to imply that there is no password. So I modified
> plugin.jelly a bit and confirmed that the correct password is indeed
> sent to the ScmStatusBean. But the call to the scm provider fails.
>
> I've tried to diff what else has happened since 1.5 was released, but
> can't find anything. The only thing that stands out is the upgrade of
> maven-scm from 1.0-alpha-1 to 1.0-alpha-2.
>
> Does anyone have a clue to what's going wrong?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] maven-scm-plugin-1.6-SNAPSHOT Error running scm:status ans
scm:prepare-release
Posted by Dennis Lundberg <de...@mdh.se>.
Brett Porter wrote:
> Dennis Lundberg wrote:
>> Does anyone have a clue to what's going wrong?
>>
>
> Not really, but I'd highly recommend:
> - upgrading to 1.0-beta-2 as a starting point
Did that, but it didn't help :(
> - debugging it by attaching a remote debuger to the maven instance. Much
> less troublesome.
I will try to set something up.
Thanks
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [m1] maven-scm-plugin-1.6-SNAPSHOT Error running scm:status ans
scm:prepare-release
Posted by Brett Porter <br...@apache.org>.
Dennis Lundberg wrote:
> Does anyone have a clue to what's going wrong?
>
Not really, but I'd highly recommend:
- upgrading to 1.0-beta-2 as a starting point
- debugging it by attaching a remote debuger to the maven instance. Much
less troublesome.
HTH,
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org