[
http://jira.codehaus.org/browse/CONTINUUM-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105100
]
Teodoro Cue Jr. commented on CONTINUUM-1387:
--------------------------------------------
That's what I've tried to do. Just put it in the build queue even if
isInCheckoutQueue returns true. But the build process would build the project
anyway. Source downloaded or not. This is the reason why I discovered that the
build process would download the project if the working directory does not
exist.
With this, would it be better to make another queue? If isInCheckoutQueue
returns true, put the project in the new queue instead of the build queue. The
new queue would implement an observer pattern listening to the checkout queue.
When a project has been checkout completely, trigger the build by calling
DefaultContinuum.buildProject().
> 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
>
> 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
