Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Received-SPF: pass (nike.apache.org: domain of alasdair.nottingham@gmail.com
 designates 209.85.216.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type;
        b=iEwnqcd9qn0qaihMwbauGAx0yJK3r14I/rLWNDk2AntcyIYew+2TIp8wP8iSzOzRoa
         j/ErQi113gZQgOi7g8PfDiT5l8v94PISxs1XbRVvLEIw8P1lYU/kMd61UOApGnYVJ4Qv
         Y9N0T0nreeuoErWM1b2dQgfYkCuobpFsXikGs=
MIME-Version: 1.0
Sender: alasdair.nottingham@gmail.com
Date: Fri, 4 Feb 2011 21:33:44 +0000
Message-ID: <AANLkTimiuRSy9KUG0JmD7kuYCjYL8xyn9KnjoxGe9VDN@mail.gmail.com>
Subject: [DISCUSSION] Using packageinfo to set package versions
From: Alasdair Nottingham <not@apache.org>
To: dev@aries.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Currently we specify versions of exported packages in the pom. This is
not ideal as it means whenever anyone makes a change in a package they
have to edit the pom, also you need to sync the version correctly
between the bundles and the uber bundles.

bnd supports the packageinfo files (and also annotations in
package-info.java), but those are not currently picked up and used in
our build. I raise FELIX-2819 and a workaround has been suggested,
which I managed to get working.

The fix would be to add the following to the default-pom and get the
modules to use the updated parent:

            <resource>
                <directory>${project.build.sourceDirectory}</directory>
                <includes>
                    <include>**/packageinfo</include>
                </includes>
            </resource>

Thoughts?
Alasdair

-- 
Alasdair Nottingham
not@apache.org