Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of bimargulies@gmail.com
 designates 74.125.82.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=I219iuZ7oL/gf/LmqnErElCvU5FGm5oSnaFj+HavbG2qymVIlCTQ5TKALvI9g9xN+4
         dl2lXQslc8cIZ+4I2xZydTfKe10Ua0jRmbILaBAdkmMLAqviIlwo7RtdDTh82n/vx4p7
         aGlWAONDLQf13Smn14BqXUglJ78NGWLvJtSk8=
MIME-Version: 1.0
Date: Sat, 6 Mar 2010 16:42:23 -0500
Message-ID: <61b5d9411003061342m502ef2ecube72b8864b6f77fa@mail.gmail.com>
Subject: Possible neatening in distribution
From: Benson Margulies <bimargulies@gmail.com>
To: CXF Dev <dev@cxf.apache.org>
Content-Type: multipart/alternative; boundary=0016e6dab0ec0e5ef1048128b5c4

--0016e6dab0ec0e5ef1048128b5c4
Content-Type: text/plain; charset=UTF-8

Having shamelessly cribbed various maven tricks from CXF into some other
project, I recently learned something. Maven 'builds' a parent project
before building its children. As a result, it's somewhat unclear why the cxf
distribution works at all.

I propose to split it, moving bundle and manifest either up to top-level or
to be children of a new directory, so that distribution can just depend on
them and the order of build operations will be clear.

--0016e6dab0ec0e5ef1048128b5c4--