Mailing-List: contact dev-help@creadur.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@creadur.apache.org
Subject: Re: [jira] [Commented] (RAT-163) Gradle Rat plugin
To: dev@creadur.apache.org
References: <JIRA.12726426.1404937608000@Atlassian.JIRA>
 <JIRA.12726426.1404937608516@arcas>
 <JIRA.12726426.1404937608000.85452.1443365464669@Atlassian.JIRA>
 <56082F68.9090900@apache.org>
 <CAOGo0Vbfmdkqcjqv3oSnHxWV5OYH+HYtifXPepfgju6MLO8pRg@mail.gmail.com>
From: "P. Ottlinger" <pottlinger@apache.org>
Message-ID: <56098CC4.2050005@apache.org>
Date: Mon, 28 Sep 2015 20:53:56 +0200
MIME-Version: 1.0
In-Reply-To: 
 <CAOGo0Vbfmdkqcjqv3oSnHxWV5OYH+HYtifXPepfgju6MLO8pRg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi *,

Am 28.09.2015 um 13:16 schrieb sebb:
> However I wonder why we bundle the Ant plugin build in with Maven.
> Ant and Maven are independent build systems.
> An Ant-only shop is forced to use Maven to build RAT.
> 
> We should probably split the project into a standalone core (CLI) and
> then have plugins for the various build systems.

That's what I mean with poor architecture - we have a strange mix of a
core component with a CLI and various components (ant and mvn at the
moment) that have a different functionality and different parameters and
so on ...

Apart from that I find it quite hard to write good tests for all this
special functionality encapsulated in maven/ant submodules.

> There will be another flavour of the month after Gradle, and trying to
> cram them all into one build seems wrong.

I'm not sure if the alternative of having one project per buildsystem is
that maintainable - following the discussion on how long we keep JDK5
compatibility I'd assume that patches would take even longer with more
projects.

However we could start discussing the separation of RAT once 0.12 is out
of the door .... maybe Paul (eskatos) can provide a patch that
integrates the gradle plugin in a JDK5-compliant manner.

We'll see ...

Phil