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.
That would certainly make Forge Console view the #1 choice for Forge developers.
Regards,
George Gastaldi
2012/5/24 Thomas Frühbeck <fruehbeck(a)aon.at>:
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