In a normal build, it's ok to use the anonymous connection, but what if I want do a mvn release using continuum, that will require checking in and tagging, therefore a developer connection is necessary, so it depends.
I think, when adding a maven project into continuum, the user should be asked to choose between the readonly anonymous connection or read-write developer connection, afterwards, continuum can read the relevent connection and use that, or report the error if the corresponding connection is N/A. One more step, if and only if the anonymous connection url and the developer connection url are the same, then, whether readonly or read-write is just the result of user authentication, anonymous results in readonly connection, whilst an authenticated user with write priviledge can get a read-write connection. So this could mean that we only need one connection url and let user select the authentication type, which determine the writability of the connection. so we may deprecate the scm.developerConnection element? hmm... Thanks Roger On 12/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > The scm.connection is the anonymous connection. So, should continuum work > with the developerConnection or the anonymous connection? (Or pick the one, > that is available) > > With regards, > > Nick Stolwijk > > > -----Original Message----- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: Wed 12/19/2007 3:24 PM > To: [EMAIL PROTECTED] > Subject: Re: Maven Site, No Anonymous Access to Source Repository > > On Dec 18, 2007 9:08 PM, Roger Ye <[EMAIL PROTECTED]> wrote: > > > and if I try to remove the scm.connection element from my pom.xml, then > I > > can not add my project into continuum using the pom, continuum reports > > I think Continuum ought to work with just an anonymous connection. > Can you check JIRA and file that if it's not there? > > -- > Wendy > >
