Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (nike.apache.org: domain of bimargulies@gmail.com
 designates 209.85.214.41 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=oaQm3Lsg8ox0b7MEK+OjXdeY7iM2klmO36sWokF/VzkMcr3szVDbNr5kunKzhJT6qq
         Pmtxgg+6jJVXY96CbPaiVgce/BTAlo94SHuYrVwC3JO6TgSCj11I77pjxLuCmzWA0HUG
         EGBQYC8vWgQGIiUjxHCBFy6gR3E0MxVd6qeZM=
MIME-Version: 1.0
Date: Fri, 29 Oct 2010 17:29:23 -0400
Message-ID: <AANLkTikbg-jgXkVZ4Eyr7beO0Vzy1tYneJrJSqq+L=nY@mail.gmail.com>
Subject: Pom editing and joining the community in general
From: Benson Margulies <bimargulies@gmail.com>
To: robert@gliesian.com, CXF Dev <dev@cxf.apache.org>
Content-Type: text/plain; charset=UTF-8

Robert,

I wouldn't want you to get the wrong impression from the comments on
your JIRA related to the top-level POM.

There is a trust issue, and it related to the essential fragility of
maven poms. You've picked the one central location where a change
could do just about maximal damage to the builds.

I've seen builds completely decompose from a plugin version update.
The Maven Gang sometimes leaves something to be desired in the testing
department.

Modulo Dan and my specific opinions about particular aspects of this,
the big question is testing. Have you tried all the profiles? On both
Maven 2.2.x and 3.0? Including -Psetup.eclipse, and the
release-building pieces?

It would be less exciting if you'd start by offering up rather more
local patches, heaven knows we've got plenty of open JIRAs. However,
if build engineering is what floats your boat, go right ahead and test
this stuff out. I'll be happy to review and apply as appropriate.

--benson