Hi Ferry,
thanks for the advice.
Setting -sources: false and subsequently adding the project to the source
lookup for debugging did the trick :).
I think you are right with the strictly speaking part, but from a developer
experience point of view I think it would be better to have a setup that
t
You could try and turn off sources and see what happens.
-sources: false
I use
-sources: ${if;${gestalt;batch};false;true}
in my Gradle build, to have sources in the bundles when building in
bndtools, and no sources when building in gradle/jenkins
On 02/02/2019 14:57, Ferry Huberts via osgi-dev
Maybe it is inconvenient, but I think that strictly speaking that is
absolutely right, since those java files correspond to what is actually
running.
On 02/02/2019 14:52, Thomas Driessen via osgi-dev wrote:
> It seems those are the .java files within the OSGI-OPT folder of the
> generated bundle/
It seems those are the .java files within the OSGI-OPT folder of the
generated bundle/.jar.
But I have no idea why Eclipse picks those up when it is debugging.
I used the enroute archetypes and didn't change anything.
Maybe it's just a setting somewhere in Eclipse that has to be changed or
within
The bigger question is why I'm the world are there java files in target?
target is the build directory. We are there source files in there?
- Ray
On Fri, Feb 1, 2019, 13:47 Paul F Fraser via osgi-dev <
osgi-dev@mail.osgi.org wrote:
> Thomas,
> Thank goodness someone else has experienced this. I
Thomas,
Thank goodness someone else has experienced this. I thought it was my problem
only.
I mentioned this on this list previously but so far no response.
Paul
On 2/02/2019 3:54 am, Thomas Driessen via osgi-dev wrote:
Hi,
now that I'm using the enroute maven workspace I stumbled upon anothe
