Re: Making scm connection optional

[jgifford <jg...@wernervas.com>]

I've ran into this issue with Continuum 1.1 and removing the 'connection'
element from the pom's repository section.  We removed the 'connection'
element because the documentation site generation features for Maven uses
that element to indicate that a repository has anonymous access.  In our
case this is totally bogus, so we removed the element to correct this
information in the site documentation that is generated.  

With the element removed, Continuum 1.1 works, but we get two builds now. 
One that always fails indicating that the
'update-project-from-working-directory' could not be executed.  With this,
the version information that is usually updated is not being updated.   The
second one is the actual build and that works as expected.

Hope this helps,

Johnathan

-- 
View this message in context: http://www.nabble.com/Making-scm-connection-optional-tp16570945p19202568.html
Sent from the Continuum - Dev mailing list archive at Nabble.com.

Re: Making scm connection optional

[jgifford <jg...@wernervas.com>]

I found this documentation on the Maven site that sheds a bit more light on
the subject and why I removed the connection element from the scm
configuration for the project.

http://maven.apache.org/plugins/maven-project-info-reports-plugin/examples/scm-report.html#How_to_exclude_SCM_anonymous_access_info

I believe the removal of the connection element is the cause of the two
build executions for a build definition.  It looks like Continuum needs the
value to read and update the project member's build information and Maven
uses to display anonymous access in the site documentation generator.  I
think a previous post to this thread asked why the URL couldn't be pulled
from the values set in Continuum.  This might be a better a choice in the
next release of Continuum.
-- 
View this message in context: http://www.nabble.com/Making-scm-connection-optional-tp16570945p19204042.html
Sent from the Continuum - Dev mailing list archive at Nabble.com.

Re: Making scm connection optional

[jgifford <jg...@wernervas.com>]

Wendy Smoak-3 wrote:
> 
> Can you explain more about getting two builds?  Do you have the
> project added twice or multiple build definitions?
> 

We do have multiple build definitions for each member project, but our
scheduler invokes only one of the build definitions.  But the Build results
for the member project has two results for any execution of that build
definition no matter if it was manually executed or scheduled.  I can send
you a screen shot if that would help.  I'm not sure I can send it through
mailing list though, so it'll have to be directly to you.

-- 
View this message in context: http://www.nabble.com/Making-scm-connection-optional-tp16570945p19203394.html
Sent from the Continuum - Dev mailing list archive at Nabble.com.

Re: Making scm connection optional

[Wendy Smoak <ws...@gmail.com>]

On Thu, Aug 28, 2008 at 8:05 AM, jgifford <jg...@wernervas.com> wrote:

> I've ran into this issue with Continuum 1.1 and removing the 'connection'
> element from the pom's repository section.  We removed the 'connection'
> element because the documentation site generation features for Maven uses
> that element to indicate that a repository has anonymous access.  In our
> case this is totally bogus, so we removed the element to correct this
> information in the site documentation that is generated.

It sounds like you've removed <scm><connection> but left
<developerConnection>.  I'm actually talking about making the entire
scm section optional for normal builds.

You can configure the scm report to use different urls than the pom
uses-- I added this because the module the site is published from is
often not the same place that you want to list as the location of the
source code.  (But I'm not sure you can _un_set the connection param--
probably if you leave it blank it's going to default back to the pom
value. :( )
 * http://maven.apache.org/plugins/maven-project-info-reports-plugin/scm-mojo.html

> With the element removed, Continuum 1.1 works, but we get two builds now.
> One that always fails indicating that the
> 'update-project-from-working-directory' could not be executed.  With this,
> the version information that is usually updated is not being updated.   The
> second one is the actual build and that works as expected.

Can you explain more about getting two builds?  Do you have the
project added twice or multiple build definitions?

-- 
Wendy