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
On Thu, May 24, 2012 at 10:19 AM, Thomas Frühbeck <fruehbeck(a)aon.at> wrote:
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
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."