[ http://jira.codehaus.org/browse/CONTINUUM-598?page=comments#action_78119 
] 
            
Wendy Smoak commented on CONTINUUM-598:
---------------------------------------

In addition to allowing a choice, Continuum should handle a <scm> element with 
no <connection> (only <developerConnection>).

Right now, it complains that <connection> is missing.  Adding <connection> 
causes the generated source-control.html web page to have an "Anonymous Access" 
section that says anyone can check out the project, which in my case is not 
true.





> Ability to specify which scm connection should be used to build the project 
> (connection or developerConnection)
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-598
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-598
>             Project: Continuum
>          Issue Type: New Feature
>          Components: Core system, Web interface, SCM
>    Affects Versions: 1.0.1, 1.0, 1.0.2
>            Reporter: Igor Vaynberg
>             Fix For: 1.1
>
>
> i am a committer on a sf.net project. the anonymous cvs access is extremely 
> unstable, but the developer access is rock solid. since i am a developer and 
> i run a continuum server i am in a position to leverage the developer scm 
> connection. it would be great if i can just tell continuum to use the 
> developerConnection scm url rather then the regular connection scm url.
> i tried chaning the url in the project info manually, but after the project 
> is built once the url reverts back to the one in the pom ( as it should i 
> would imagine )
> i think a simple drop down in project info with 
> connection/developerConnection choice would be great

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to