[forge-dev] FORGE-568 "Allow running/debugging Forge in eclipse" opinion quest

[Max Rydahl Andersen]

> 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

if they are all with maven metadata our maven repository lookup should work fine for that.

https://community.jboss.org/en/tools/blog/2012/01/24/jboss-source-lookup

>     - and of course most interesting: the lookup of sources which are used by Forge during debug - that will be real fun :-))

This one is tricky and we can easily end up in a mess of duplicate configuration - not sure how we can do this efficiently without
introducing a 'forge' eclipse project type.

maybe a simlpe "Add these projects on Forge classpath" in the runtime configuration would be sufficient.

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

https://jira.jboss.org/jira/browse/JBIDE is the king of all jboss tools source code contributions :)

btw. this most likely won't make it into our upcoming release (we just had codefreeze) but we should surely look at it to
see if doable to include in a update or if it has to go onto JBoss tools 3.4.x (targeting eclipse Juno)

/max


> 
> 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 at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev