Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: 
 <4464926.206801242344624915.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Thu, 14 May 2009 18:43:44 -0500 (CDT)
From: "Wendy Smoak (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [jira] Created: (CONTINUUM-2232) Continuum ignores duplicate
 projects in forced and scheduled builds
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Continuum ignores duplicate projects in forced and scheduled builds
-------------------------------------------------------------------

                 Key: CONTINUUM-2232
                 URL: http://jira.codehaus.org/browse/CONTINUUM-2232
             Project: Continuum
          Issue Type: Bug
    Affects Versions: 1.3.2
            Reporter: Wendy Smoak


When there are duplicate projects being built at one time, Continuum ignores the duplicates and only builds one of them.  (See ProjectSorter.java)  It prints a log message, but there is nothing visible in the web ui.

Continuum considers projects with the same groupId:artifactId:version as duplicates, so for example you can't built both the trunk and a branch with the same version in the one group (or even in different groups if they are on the same build schedule.)

It should probably warn if you add duplicates to a group.

If you click 'build all' and it is *not* going to build everything, it should tell you.

For scheduled builds there should be some indication of why a project was not 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