Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.220.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJSjvwtfE5CW=8v59BNEC5hCkuLtbA4frAud6hm3mqXKvNUayg@mail.gmail.com>
References: 
 <CAJSjvwtfE5CW=8v59BNEC5hCkuLtbA4frAud6hm3mqXKvNUayg@mail.gmail.com>
Date: Fri, 27 Jul 2012 10:56:42 +0100
Message-ID: 
 <CAOGo0Va_SWJY+M=iCA3p-BZxSQJPgtgAHVw4tG+yKuKUvsu=iQ@mail.gmail.com>
Subject: Re: JIRA plugin in hudson for commons-collections
From: sebb <sebbaz@gmail.com>
To: builds@apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 27 July 2012 10:35, Thomas Neidhart <thomas.neidhart@gmail.com> wrote:
> Hi,
>
> I recently worked a lot on commons-collections, and the jira plugin of
> hudson is very annoying and confusing.
> The build may fail for any reason (not necessarily related to a code
> checkin) but the plugin will add comments to all issues that are listed in
> the commits since the last build.
>
> Would it be possible to disable this plugin as it causes more problems than
> it solves?

+1

Or is it possible for the plugin to be optional, with a default of not
active, so projects could elect to use it?

> Thanks,
>
> Thomas