Hi, browsing the issues of Forge I found this one: https://issues.jboss.org/browse/FORGE-568 It would be most easily done by a small change of /core/dist/pom.xml in the "runForge" profile. To make the setup easier it is necessary to make eclipse think it's a java project, AFAIK by adding the JavaNature in project.xml. Even more simplified would be a locally stored eclipse run configuration file, making the setup a "one-line-howto" :-) My question is: is it acceptable to commit IDE specific files in the core/dist/ directory? Files namely: /dist/.project.xml /dist/runForge.launch Thomas _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Sorry if I wasnt clear enough - no complications AFAICS, nothing to do really. All you need is to call the exec:java in the forge-distribution, because there all modules are available. It totally feels like any other maven Java project. Want to have a go with it? Files attached, put in /core/dist/ runForge.launch -> RunAs ->m2 runForge          or         DebugAs->m2 runForge yet unsolved: the current working dir is /core/dist/ too - unfortunately May be solved by putting it in another maven project.. Am 24.05.2012 16:31, schrieb Lincoln Baxter, III: > TBH I'm not really sure of the complications involved here. We used to > have a mvn exec:java profile in the shell project, but the problem there is > the lack of modularity. We'd need to write another bootstrap class that does > not depend on JBoss Modules. > > ~Lincoln _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Gorge, great idea, I think I get the point, I was too much focused on developing Forge core, but this shouldnt be the most popular use case for Forge :-) Any idea where I can get the source? Thomas Am 24.05.2012 19:05, schrieb George Gastaldi: > > Hi Thomas, > > Instead of using these specific files, it would be better if the Forge > Console View itself could do this trick, by using the classpath > provided by Eclipse + M2. >

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 testing plugins. Thomas, the source code for the Eclipse integration of Forge is in http://anonsvn.jboss.org/repos/jbosstools/trunk/forge. 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 ;-) Cheers, Koen 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. > > Regards, > > George Gastaldi > > 2012/5/24 Thomas Frühbeck <fruehbeck(a)aon.at&gt;: >> Gorge, >> >> great idea, I think I get the point, I was too much focused on developing >> Forge core, but this shouldnt be the most popular use case for Forge :-) >> Any idea where I can get the source? >> >> Thomas >> Am 24.05.2012 19:05, schrieb George Gastaldi: >>> >>> Hi Thomas, >>> >>> Instead of using these specific files, it would be better if the Forge >>> Console View itself could do this trick, by using the classpath >>> provided by Eclipse + M2. >>> >> > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

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 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. > > /max > > 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 testing plugins. >> >> Thomas, the source code for the Eclipse integration of Forge is in http://anonsvn.jboss.org/repos/jbosstools/trunk/forge. 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 ;-) >> >> Cheers, >> Koen >> >> 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. >>> >>> Regards, >>> >>> George Gastaldi >>> >>> 2012/5/24 Thomas Frühbeck <fruehbeck(a)aon.at&gt;: >>>> Gorge, >>>> >>>> great idea, I think I get the point, I was too much focused on developing >>>> Forge core, but this shouldnt be the most popular use case for Forge :-) >>>> Any idea where I can get the source? >>>> >>>> Thomas >>>> Am 24.05.2012 19:05, schrieb George Gastaldi: >>>>> >>>>> Hi Thomas, >>>>> >>>>> Instead of using these specific files, it would be better if the Forge >>>>> Console View itself could do this trick, by using the classpath >>>>> provided by Eclipse + M2. >>>>> >>>> >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

and a screen shot just to show that it's not a fake :-) Thomas _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

and finally the sources of the plugins, for the interested reader. Thomas _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

and a screen shot just to show that it's not a fake :-) Thomas <EclipseForgeDebug.png> _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev