SVN checkout from snapshot
0 views
Skip to first unread message
Phil Richards
Jan 30, 2008, 9:10:14 AM1/30/08
to Vulcan Users
Hi all,
I just downloaded the latest snapshot (as of 30/01/08) in order to
evaluate using vulcan with nant. However, vulcan fails on checkout
from SVN, with the error:
The repository adaptor encountered an error: svn: Authentication
required for '<http://servername:80> svn'
And I made sure that the username and password supplied in SVN config
are correct. So it _looks_ like vulcan isn't supplying them to the SVN
server... is this a known bug? I couldn't find it in the issues list.
Or am I missing something?
Cheers,
Phil
I just downloaded the latest snapshot (as of 30/01/08) in order to
evaluate using vulcan with nant. However, vulcan fails on checkout
from SVN, with the error:
The repository adaptor encountered an error: svn: Authentication
required for '<http://servername:80> svn'
And I made sure that the username and password supplied in SVN config
are correct. So it _looks_ like vulcan isn't supplying them to the SVN
server... is this a known bug? I couldn't find it in the issues list.
Or am I missing something?
Cheers,
Phil
Chris Eldredge
Jan 30, 2008, 10:00:05 AM1/30/08
to vulcan...@googlegroups.com
Hey Phil,
I know it was working at one point but none of my current projects require authentication for read-access. I just did a quick test and sure enough it looks like it is broken.
I have opened a bug report to look into the issue:
http://code.google.com/p/vulcan/issues/detail?id=125
I'll probably have this fixed in the next couple days, as long as its easy enough to figure out the problem.
Chris
I know it was working at one point but none of my current projects require authentication for read-access. I just did a quick test and sure enough it looks like it is broken.
I have opened a bug report to look into the issue:
http://code.google.com/p/vulcan/issues/detail?id=125
I'll probably have this fixed in the next couple days, as long as its easy enough to figure out the problem.
Chris
Phil Richards
Jan 30, 2008, 10:15:07 AM1/30/08
to Vulcan Users
Cool, thanks for the quick reply. I'll keep an eye out for the fix!
Cheers,
Phil
On Jan 30, 3:00 pm, "Chris Eldredge" <chris.eldre...@gmail.com> wrote:
> Hey Phil,
>
> I know it was working at one point but none of my current projects require
> authentication for read-access. I just did a quick test and sure enough it
> looks like it is broken.
>
> I have opened a bug report to look into the issue:http://code.google.com/p/vulcan/issues/detail?id=125
>
> I'll probably have this fixed in the next couple days, as long as its easy
> enough to figure out the problem.
>
> Chris
>
Cheers,
Phil
On Jan 30, 3:00 pm, "Chris Eldredge" <chris.eldre...@gmail.com> wrote:
> Hey Phil,
>
> I know it was working at one point but none of my current projects require
> authentication for read-access. I just did a quick test and sure enough it
> looks like it is broken.
>
> I have opened a bug report to look into the issue:http://code.google.com/p/vulcan/issues/detail?id=125
>
> I'll probably have this fixed in the next couple days, as long as its easy
> enough to figure out the problem.
>
> Chris
>
Chris Eldredge
Jan 30, 2008, 11:55:09 AM1/30/08
to vulcan...@googlegroups.com
Phil,
I found the problem. I changed some of the code to use the JavaHL api, and wasn't providing the credentials in the new implementation.
If you download the snapshot again, it should start working.
Cheers,
Chris
I found the problem. I changed some of the code to use the JavaHL api, and wasn't providing the credentials in the new implementation.
If you download the snapshot again, it should start working.
Cheers,
Chris
Phil Richards
Jan 30, 2008, 3:19:45 PM1/30/08
to Vulcan Users
Awesome, thanks Chris.
On Jan 30, 4:55 pm, "Chris Eldredge" <chris.eldre...@gmail.com> wrote:
> Phil,
>
> I found the problem. I changed some of the code to use the JavaHL api, and
> wasn't providing the credentials in the new implementation.
>
> If you download the snapshot again, it should start working.
>
> Cheers,
>
> Chris
>
On Jan 30, 4:55 pm, "Chris Eldredge" <chris.eldre...@gmail.com> wrote:
> Phil,
>
> I found the problem. I changed some of the code to use the JavaHL api, and
> wasn't providing the credentials in the new implementation.
>
> If you download the snapshot again, it should start working.
>
> Cheers,
>
> Chris
>
Reply all
Reply to author
Forward
0 new messages