>> I wonder if you are at all interested in this contribution. I believe it'll be very useful for debugging applications
This will be good to have. Right now, I had a quick glance on the *.pde folder.
Hopefully there are no extra dependencies etc. I will create a bug on PDE and add
you on CC to take this forward.
----- Original message -----
From: Igor Fedorenko <igor@xxxxxxxxxxxxxx>
Sent by: pde-dev-bounces@xxxxxxxxxxx
To: Sarika Sinha/India/IBM@IBMIN, "Eclipse JDT Debug developers list." <jdt-debug-dev@xxxxxxxxxxx>
Cc: m2e-dev@xxxxxxxxxxx, pde-dev@xxxxxxxxxxx
Subject: Re: [pde-dev] [jdt-debug-dev] Offer to contribute advanced source lookup implementation
Date: Wed, Oct 19, 2016 6:01 AM
Thank you for your interest, Sarika, I'll try to create gerrit code review in next couple of weeks, time permitting.
@pde-dev, I realize you are very busy, but I wonder if you are at all interested in this contribution. I believe it'll be very useful for debugging applications that use both equinox and url classloaders, like m2e or tycho.
On Tue, Oct 18, 2016, at 09:48 AM, Sarika Sinha wrote:
Sounds interesting !!
Thanks,
Sarika
Igor Fedorenko ---10/08/2016 05:32:29 PM---Over last several years I implemented what I call "advanced source lookup", which I would like to co
From: Igor Fedorenko <igor@xxxxxxxxxxxxxx>
To: jdt-debug-dev@xxxxxxxxxxx, pde-dev@xxxxxxxxxxx, m2e-dev@xxxxxxxxxxx
Date: 10/08/2016 05:32 PM
Subject: [jdt-debug-dev] Offer to contribute advanced source lookup implementation
Sent by: jdt-debug-dev-bounces@xxxxxxxxxxx
Over last several years I implemented what I call "advanced source
lookup", which I would like to contribute to Eclipse.
From user perspective, the advanced source lookup provides correct
source lookup when runtime classpath is not fully known in advance
and/or contains multiple versions of the same class. It also downloads
sources archives from remote artifact repositories automatically when
they are needed. No manual source lookup path configuration is needed.
In other words, the source lookup just works (at least it fails far less
frequently).
Internally, the implementation uses javaagent to capture exact location
of the running code in a custom JSR45 stratum. When source lookup is
requested by the debugger, the captured location is matched to one of
workspace projects, their dependencies or artifacts in the remote
artifact repositories. If needed, the corresponding sources archive is
located locally or downloaded from remote repoitories. Currently
implementation supports JDT java, Maven and PDE projects, but support
for other project types can be added via an extension point. Only Maven
remote repositories are currently supported, but other repository types
can be supported via extension point too (I hope somebody will implement
P2 support, for example).
The code is currently hosted at Github [1]. I think it makes sense to
split the code among JDT/Debug, which will provide general
infrastructure and extension points, PDE, which will provide support for
Plug-In projects and P2 repositories and M2E, which will provide support
for Maven projects and repositories.
I'd like to know if JDT and PDE developers are interested to accept this
contribution and what are the steps to make it happen. (I know M2E is
fully onboard with the idea :-) ).
Thank you in advance.
--
Regards,
Igor
[1] https://github.com/ifedorenko/com.ifedorenko.m2e.sourcelookup_______________________________________________
jdt-debug-dev mailing list
jdt-debug-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/jdt-debug-dev
_______________________________________________
jdt-debug-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
