This is a really great idea! Fantastic!
On Sat, May 26, 2012 at 5:49 AM, Koen Aers <koen.aers(a)gmail.com> wrote:
Yes, that's actually a good idea. It would also be cool if we
the classes being worked upon directly in the class/module path of this
Forge launch, but I guess that will not be so easy…
Op 26-mei-2012, om 00:20 heeft Max Rydahl Andersen het volgende geschreven:
> Koen, for 3.3.x a simple control over the vm flags could be doable.
> For 3.4.x I would say we consider exposing the underlying eclipse launch
configurations for them...then you can just use the launch config editor.
> On May 24, 2012, at 20:50 , Koen Aers wrote:
>> Hi guys,
>> As George said, the initial idea for this issue is to have a mechanism
(probably an Eclipse preference setting) to make sure that Forge start in
debug mode and that the Eclipse debugger gets attached automatically. It
would not only help for core development but also while developing and
>> Thomas, the source code for the Eclipse integration of Forge is in
. The launching of
Forge and the definitions of preferences are in the
org.jboss.tools.forge.core plugin. Preference panels are in the
org.jboss.tools.forge.core.ui plugin. If you really want to have a stab at
this, feel free to nag me on irc ;-)
>> Op 24-mei-2012, om 19:51 heeft George Gastaldi het volgende geschreven:
>>> I think Koen Aers may help with it. Just added him to the discussion
>>> to make him aware of it.
>>> George Gastaldi
>>> 2012/5/24 Thomas Frühbeck <fruehbeck(a)aon.at>:
>>>> great idea, I think I get the point, I was too much focused on
>>>> Forge core, but this shouldnt be the most popular use case for Forge
>>>> Any idea where I can get the source?
>>>> Am 24.05.2012 19:05, schrieb George Gastaldi:
>>>>> Hi Thomas,
>>>>> Instead of using these specific files, it would be better if the
>>>>> Console View itself could do this trick, by using the classpath
>>>>> provided by Eclipse + M2.
>>> forge-dev mailing list
>> forge-dev mailing list
> forge-dev mailing list
forge-dev mailing list