I agree that this is a usability issue that should be fixed in the tool. It’s just not practical to expect everybody to adopt the convention of putting source under OSGI-OPT.
Neil > On 23 Apr 2017, at 15:21, Thomas Watson <[email protected]> wrote: > > I think including source is fine. > > Did you mean OSGI-OPT instead of OSGI-INF. The spec recommends OSGI-OPT be > used to include source. > > 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? > > Tom. > > On Sun, Apr 23, 2017 at 2:13 AM, David Jencks <[email protected]> > wrote: > >> Working on FELIX-5618 I couldn’t 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’d like to include the sources for DS in OSGI-INF as >> recommended by Peter et al. I’d 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. >> >> Any objections? >> >> thanks >> david jencks >> >>
