<div dir="ltr">Hmm, that does seem like an integration problem. My recommendation would be against using mvn eclipse:eclipse, but rather "File --> Import --> Existing Maven Project"<div><br></div><div>If that option is not available, that is likely also the reason why the import did not work in the first place. I hope this helps! Let us know if it works :)</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 18, 2013 at 3:24 PM, <span dir="ltr"><<a href="mailto:forge-users@lists.jboss.org" target="_blank">forge-users@lists.jboss.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">[Meta: if the answer to this is "RTFM", where is it that I should have looked?]<br>
<br>
I'm a quiche-eating IDE user, so I'm running Forge in JBoss Tools 4.1 (on Eclipse 4.3.1), not standalone.<br>
<br>
If I use the Forge version (1.3.3) that was bundled with JBoss Tools, all is good: Forge "new-project" automagically generates the appropriate Eclipse artifacts (.classpath and .project), and Eclipse recognizes and displays the project.<br>
<br>
I downloaded and unzipped Forge 1.4.2 and, in Eclipse Window -> Preferences, used Forge -> Installed Forge Runtimes to add the unpacked Forge 1.4.2 runtime and mark it as the default runtime to use.<br>
<br>
With that setup, Forge 1.4.2 starts up fine in Eclipse and "new-project" generates a new Maven project. But it doesn't have any Eclipse artifacts, so not surprisingly the project is invisible to Eclipse.<br>
<br>
Probably the missing automagic is something really simple (at a guess, perhaps the embedded 1.3.3 knows it should run "mvn eclipse:eclipse" and does that, whereas perhaps my unpacked 1.4.2 doesn't get the message to do that?), but:<br>
1. Is there something I should have configured somewhere so that the Eclipse-artifact automagic "just works" for e.g. my unpacked Forge 1.4.2 runtime, or<br>
2. If #1 is a non-starter, should I just remember to intone something (e.g. "mvn eclipse:eclipse"?) after "new-project", or is there more to it than that?<br>
<br>
Just for grins I tried "mvn eclipse:eclipse", which did indeed generate .classpath, .project etc but still didn't make the project visible to Eclipse (even after an Eclipse restart), so presumably there's something else needed, maybe in the .metadata for the Eclipse workspace?<br>
<br>
Posted by forums<br>
Original post: <a href="https://community.jboss.org/message/842366#842366" target="_blank">https://community.jboss.org/message/842366#842366</a><br>
<br>
_______________________________________________<br>
forge-users mailing list<br>
<a href="mailto:forge-users@lists.jboss.org">forge-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-users" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-users</a></blockquote></div><br><br clear="all"><div><br></div>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>
"Simpler is better."
</div>