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 heavy@ungoverned.org
 designates 69.89.20.192 as permitted sender)
Message-ID: <46F80873.3090907@ungoverned.org>
Date: Mon, 24 Sep 2007 14:56:51 -0400
From: "Richard S. Hall" <heavy@ungoverned.org>
User-Agent: Thunderbird 2.0.0.5 (X11/20070727)
MIME-Version: 1.0
To: dev@felix.apache.org
Subject: Re: unable to build Felix from clean repository
References: <81f0d9c0709241136k68e41719n1a4ceec81610e5e8@mail.gmail.com>
In-Reply-To: <81f0d9c0709241136k68e41719n1a4ceec81610e5e8@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I guess it sounds reasonable to me.

-> richard

Stuart McCulloch wrote:
> Hi, me again :)
>
> there's been an unfortunate side-effect of adding the OBR plugin to the
> bundle life-cycle...
>
>    maven-bundle-plugin has a dependency on maven-obr-plugin
>    maven-obr-plugin has a dependency on bundlerepository
>    bundlerepository has packaging bundle
>       ... which needs maven-bundle-plugin to build :(
>
> I have a solution that I've tested locally:
>
>    create a new sub-project called 'org.osgi.service.obr' and move
> bundlerepository/src/main/java/org/osgi/service/obr/*.java to it
>    - org.osgi.service.obr will be a standard Jar containing the OSGi OBR
> service API
>
>    add 'org.osgi.service.obr' as a dependency to bundlerepository and
> maven-obr-plugin (it replaces the bundlerepository dependency)
>
>    replace the 'org.osgi.core' dependency in maven-obr-plugin with
> org.osgi:osgi_R4_core (ie. the non-bundle artifact from central)
>
>    add 'org.osgi.service.obr' to the plugin build phase
>
> and trunk can once again build from scratch
>
> so any comments - should I open a JIRA issue for this, or go ahead and
> commit my changes?
>
>