Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
To: dev@commons.apache.org
From: =?UTF-8?B?SsO2cmc=?= Schaible <joerg.schaible@gmx.de>
Subject: Re: [RNG] Build succeeds locally but fails on Travis-CI
Date: Tue, 22 Nov 2016 02:00:40 +0100
Lines: 17
Message-ID: <o105bk$9c8$1@blaine.gmane.org>
References: <dfd79bcbb9817914764a1cf1a9c77d19@scarlet.be> <o1013g$skb$1@blaine.gmane.org> <fd034d6877e3b047812673067e0eae09@scarlet.be> <CACZkXPwRrsZoRiMpV_8E3HTvwTAO+CrdOtEcSS-b+g_cDCiM7w@mail.gmail.com>
Reply-To: joerg.schaible@gmx.de
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8Bit
User-Agent: KNode/4.14.10
archived-at: Tue, 22 Nov 2016 01:00:52 -0000

Hi Gary,

Gary Gregory wrote:

> Why not put all this stuff in your parent POM?

Parent project is the last to build. IMHO we need an own independent 
component for that. IIRC, those resources are not really commons-rng 
specific and might be useful for other commons components also. We already 
have build related components in commons (proper) and we always used lazy 
consensus for a release of those (commons-parent, commons-build-plugin, 
commons-skin, ...). commons-build seems abandonned anyway, as it is still a 
Maven 1 project. Why not simply replace that one?

Cheers,
Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org