Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
From: David Jencks <david.a.jencks@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Including sources in bundles
Date: Sun, 23 Apr 2017 08:36:41 -0700
References: <607751BC-E6AA-42F3-8987-EB871C7E8796@gmail.com>
 <CACmMR0MrvzXsWZrD=eY7Gd_Pcc-WSUYfYYQ+YrU_2-NnzjQLFA@mail.gmail.com>
To: dev@felix.apache.org
In-Reply-To: <CACmMR0MrvzXsWZrD=eY7Gd_Pcc-WSUYfYYQ+YrU_2-NnzjQLFA@mail.gmail.com>
Message-Id: <C2DC165B-E965-4790-9DB9-E0FA1705083A@gmail.com>
archived-at: Sun, 23 Apr 2017 15:36:56 -0000

I mean OSGI-OPT.

The source jars for released versions are at maven central, but I was =
debugging trunk, and the source jars aren=E2=80=99t built automatically =
(and, actually I thought of adding source to the bundle and didn=E2=80=99t=
 think of building the source jar).  Wrong list =E2=80=94 but would =
dragging/dropping a source jar into the bndtools =E2=80=9Clocal=E2=80=9D =
repo add it to the existing bundle? =20

I still think that having one artifact rather than two is more =
convenient, even if bndtools finds a source jar next to any bundle you =
drag and drop into a repository.

thanks
david jencks

> On Apr 23, 2017, at 7:21 AM, Thomas Watson <tjwats@gmail.com> wrote:
>=20
> I think including source is fine.
>=20
> Did you mean OSGI-OPT instead of OSGI-INF.  The spec recommends =
OSGI-OPT be
> used to include source.
>=20
> I am concerned that bndtools makes it hard for one such as you to =
debug our
> code.  If it is hard for you then it is impossible for the masses.  =
This
> seems like a pretty big usability issue in bndtools.  Are not the =
source
> jars published to maven central for the tools to find?
>=20
> Tom.
>=20
> On Sun, Apr 23, 2017 at 2:13 AM, David Jencks =
<david.a.jencks@gmail.com>
> wrote:
>=20
>> Working on FELIX-5618 I couldn=E2=80=99t figure out a way to debug DS =
in bndtools
>> without modifying the DS bundle to include sources.  This is =
certainly the
>> easiest way to get the sources visible in a bndtools environment.  =
After
>> this experience I=E2=80=99d like to include the sources for DS in =
OSGI-INF as
>> recommended by Peter et al.  I=E2=80=99d like to include the sources =
in the util
>> jar as well, I think then the extender base classes will show up in =
the DS
>> bundle.
>>=20
>> Any objections?
>>=20
>> thanks
>> david jencks
>>=20
>>=20