Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of gnodet@gmail.com designates
 209.85.220.212 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=rJ4I0YE9j0uhTKHEBvRpjz+64dQikikTX+spzCgFLENvBdq3gCnItbaNn6z+YB+a0S
         yvl4gLK0gfXU8egLUzOblCkRmSBHuXZamidRQEOFBV6/liJ664YfphA9yX9mkMEe5+aT
         2YhCOn5H4NGvVEcebHXt0dF9EkWKH8ICZVzC8=
MIME-Version: 1.0
In-Reply-To: <C52B5658-6949-4F78-8113-46428B4BE077@yahoo.com>
References: <DB9721DA-51B6-4E2D-853D-D9689E6CF359@yahoo.com>
	 <b23ecedc1002242235w3b0b75bep773660134d902ba0@mail.gmail.com>
	 <C52B5658-6949-4F78-8113-46428B4BE077@yahoo.com>
Date: Thu, 25 Feb 2010 09:41:07 +0100
Message-ID: <b23ecedc1002250041x37b7f87fg62cf745465bc58c9@mail.gmail.com>
Subject: Re: Why are obr.xml files next to pom.xml?
From: Guillaume Nodet <gnodet@gmail.com>
To: aries-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 25, 2010 at 09:00, David Jencks <david_jencks@yahoo.com> wrote:
> Is this some standard I'm not aware of? =A0What are these used for? =A0Ho=
w?
> =A0When? =A0Is this documented somewhere? =A0They look like repository.xm=
l files,
> is there a good reason for not naming them repository.xml? =A0And how do =
they
> differ from what the bundle plugin generates for a bundle?

Those are fragments that are used by the bundle plugin to generate addition=
al
requirements and capabilites.  I've introduced them because the syntax for
the Export-Service / Import-Service headers is insufficient to capture all =
the
semantics.  Those fragments are used to generate the repository.xml in your
  ~/.m2/repository/repository.xml

FWIW, I've kept the headers because even if they do not capture the whole
semantic, it still gives a good idea.

One idea that has been proposed is also to enhance the maven bundle plugin
to introspect blueprint bundles so as to find out which services are import=
ed
and exported.  I suppose when it's done, those OBR files can be removed and
maybe even the headers if they are generated.

Makes sense ?

> In geronimo we're experimenting with building up a bundle repository from
> repository.xml, embedded in geronimo plugins, that are constructed from t=
he
> maven dependencies of the plugin. =A0Our hope is that this will give cont=
rol
> over the repository contents visible to the server yet allow it to be
> extensible based on what is installed into the server.

I have a small tool on my computer (a hacked version of bindex) which
can be used
to scan a maven repository and turn it into a repository.xml with mvn:
urls in case
you're interested.

> thanks
> david jencks
>
> On Feb 24, 2010, at 10:35 PM, Guillaume Nodet wrote:
>
>> Nothing, but that's part of the definition of the bundle, not really
>> it's content per se, so I was thinking it make sense to put it there,
>> but i'd have no problem in moving it in src/main/resources. =A0Actually,
>> I think it's embedded =A0in the jar, but that's only because I did not
>> found a way not to.
>>
>> On Wed, Feb 24, 2010 at 23:54, David Jencks <david_jencks@yahoo.com>
>> wrote:
>>>
>>> What is so special about obr.xml files that they aren't in
>>> src/main/resources?
>>>
>>> thanks
>>> david jencks
>>>
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>
>


--=20
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com