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

[Thomas Frühbeck]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pom.xml
Type: text/xml
Size: 16173 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/forge-dev/attachments/20120524/926ad2c3/attachment-0003.xml 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: runForge.launch
Type: text/xml
Size: 9562 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/forge-dev/attachments/20120524/926ad2c3/attachment-0004.xml 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .project
Type: text/xml
Size: 747 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/forge-dev/attachments/20120524/926ad2c3/attachment-0005.xml