You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Teodoro Cue Jr. (JIRA)" <ji...@codehaus.org> on 2007/08/23 08:18:47 UTC

[jira] Updated: (CONTINUUM-1387) Can't initiate a build of a new project in continuum until all modules have been checked out

     [ http://jira.codehaus.org/browse/CONTINUUM-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Teodoro Cue Jr. updated CONTINUUM-1387:
---------------------------------------

    Attachment: CONTINUUM-1387.patch

Using Jesse's solution, I was able to add a new remove() method on plexus-taskqueue and used that on DefaultContinuum to remove the task on the checkout queue.

Patch attached. But it is dependent on PLXCOMP-82.

> Can't initiate a build of a new project in continuum until all modules have been checked out
> --------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-1387
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1387
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1-beta-1
>            Reporter: Wendy Smoak
>            Assignee: Teodoro Cue Jr.
>         Attachments: CONTINUUM-1387.patch
>
>
> When a multi-module project is added to continuum, a working copy of each module is extracted from subversion.
> Typically after adding a project I want to kick off a build.
> If I initiate the build before all the modules are extracted, the ones that have not yet been fully extracted will not be queued for build. Only those already fully extracted will be built.

-- 
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