TBH I&#39;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&#39;d need to write another bootstrap class that does not depend on JBoss Modules.<br>
<br>~Lincoln<br><br><div class="gmail_quote">On Thu, May 24, 2012 at 10:19 AM, Thomas Frühbeck <span dir="ltr">&lt;<a href="mailto:fruehbeck@aon.at" target="_blank">fruehbeck@aon.at</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
browsing the issues of Forge I found this one:<br>
<a href="https://issues.jboss.org/browse/FORGE-568" target="_blank">https://issues.jboss.org/browse/FORGE-568</a><br>
<br>
It would be most easily done by a small change of /core/dist/pom.xml in<br>
the &quot;runForge&quot; profile.<br>
To make the setup easier it is necessary to make eclipse think it&#39;s a<br>
java project, AFAIK by adding the JavaNature in project.xml.<br>
Even more simplified would be a locally stored eclipse run configuration<br>
file, making the setup a &quot;one-line-howto&quot; :-)<br>
<br>
My question is: is it acceptable to commit IDE specific files in the<br>
core/dist/ directory?<br>
<br>
Files namely:<br>
     /dist/.project.xml<br>
     /dist/runForge.launch<br>
<br>
Thomas<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>&quot;Simpler is better.&quot;<br>