Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (athena.apache.org: domain of fmeschbe@gmail.com designates
 209.85.220.211 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=WmyQTlkupVLjzd1zE2hvt23CXzJujlmLMfxi/cTg0ElfjnwTIcD7Z7vkP7rJ5YYWbW
         nnthorB5XaH52kdx9hgJU15KiHzH1pXMjyydC7ncLhJOqAHjQUhB6vB+8aFw50oycqZ2
         voQpRqp+MgUr/SdDOtYWoOhGb7ivTIL4dUHm4=
Message-ID: <49E9A05D.9010604@gmail.com>
Date: Sat, 18 Apr 2009 11:41:49 +0200
From: Felix Meschberger <fmeschbe@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090320)
MIME-Version: 1.0
To: dev@felix.apache.org
Subject: Re: Next release of the Felix parent pom [1.1.0]
References: <81f0d9c0904171840v7bb19998g63d2c77afe0bf111@mail.gmail.com>
In-Reply-To: <81f0d9c0904171840v7bb19998g63d2c77afe0bf111@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Stuart,

Stuart McCulloch schrieb:
> Hi,
> 
> I'd like to stage a new release of our parent pom (ie. pom/pom.xml) - this
> will exercise the new release process.
> Are there any objections to starting this? Does anyone have any changes they
> would like to make to this pom?
> 
> Note that this isn't a vote on the actual release - I will start that once
> I've staged it using Nexus.
> 
> Also please hold off from any new releases until I've tried out the new
> process and documented it on the wiki :)

Can we split the parent pom (definitions pertaining to all Felix
projects) and reactor (<modules> section) functionalities into into two
files by that matter ?

We could for example create a reactor project at trunk, which stays at
SNAPSHOT version for ever and which we can update as we see fit to
accomodate new child projects.

The actual parent pom would remain where it was and would be updated and
released for release new general setup such as the deployment configuration.

In addition it is IMO also a matter of separation of concerns (reactor
vs. general setup). We have done this in the Sling and Jackrabbit
projects with much success (IMHO).

Regards
Felix