Guys,

Thomas Frühbeck has done an incredible job enabling this DEBUG feature in JBoss Tools. It has only just been committed to trunk so it will unfortunately not make it into the soon-to-be-released JBT 3.3.0. 

Anyway, as soon as trunk is picked up again for the nightly builds (probably after the 3.3.0 release), you will be able to use a preference on the Forge preference pages to launch the embedded (or any other) Forge runtime in DEBUG mode. If you set a breakpoint somewhere in the plugin code or Forge core code that you are working on, execution will stop as expected. The feature is still a bit rough around the edges as you will need to add the projects in your workspace to the source lookup path every time Forge is launched but we are working on a solution for that problem.

It's also not (yet) possible to hot-replace the code you are working on. That's also something for the future if it's somewhat doable.

But as it is now this is already a super great tool that will be very helpful for everybody working on Forge plugins or on the runtime. Big kudos to Thomas for working himself into this codebase so quickly and implementing this feature that is far from trivial!

Thanks Thomas!

Cheers,
Koen

Op 29-mei-2012, om 00:36 heeft Thomas Frühbeck het volgende geschreven:

OK, the size limit killed me, another go to send this message:

Hi,

I just finished a first draft of the ForgeConsole in Debug mode.

The loading of the embedded Forge runtime ist still not working, this needs real experts :-/
So if you would like to give it a try, pleas load your own runtime in the Forge preferences.

The implementation is still a bit shaky, but at least the direction seems to be clear.
Still missing:
    - automatic source lookup of Forge sources in eclipse
    - and of course most interesting: the lookup of sources which are used by Forge during debug - that will be real fun :-))

Load the attached plugin: unzip in <eclipse-home>/dropins/
To run the DebugForge: [SHIFT]+[CTRL]+[4] 

Please find attached:
    - the zip of the plugin for dropins folder
    - the source I adapted included in the soure.jar files will come in separate message

So, how do we go from here, to whom can I pass over the sources for quality check / check-in?

Any ideas welcome,
Thomas
   

Am 26.05.2012 19:51, schrieb Lincoln Baxter, III:
This is a really great idea! Fantastic!

On Sat, May 26, 2012 at 5:49 AM, Koen Aers <koen.aers@gmail.com> wrote:
Yes, that's actually a good idea. It would also be cool if we could pickup the classes being worked upon directly in the class/module path of this Forge launch, but I guess that will not be so easy…

Cheers,
Koen



<forge.zip>_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev