JBoss Tools and initial setup woes

[bolke]

I am trying to move over to the new project layout in jboss tools to reap the benefits of hot-deploy. To be honest I don't really like the division into 4 seperate projects (it has issues in version control), but everything has its pros and cons.

However I just downloaded the latest eclipse (JEE), jboss tools 2, seam 2 and jboss as 4.2.2 on OSX 10.5.2. So it is a clean install. Now, when I create a new project all goes fine. Then when I try to deploy the server bails out with cannot open jboss-seam.jar. The server is correct as the ear libraries are quite unexpectedly not found within the deployed ear. Is there a way to resolve this?

cheers.

[tony.herstell1]

I have been using exploded deployment for over a year with MyEclipse.

I have to have three projects (all separate in CM)
Ear, EJB and War. I Link the War and EJB back to the Ear (which nicely also means they can share the required jars in the .EAR).

From there its a simple one-click to run the server and as long as I don't change a method sig or change an .xml config file I can pretty much keep coding and not have to restart the server and just keep working. No Build-Deploy stage EVER!

So; what worries me is what this fourth project required for JBoss Tools is?

I was thinking (and even trying) of checking it out but don't want to move too far from what I have got working with MyEclipse as its so great (imho anyway). Since JBoss tools won't install on MyEclipse (summat to do with one file deployment) then I can't unless I download a basic Eclipse which I really don't want to do (MyEclipse has soooo many useful tools built in).

[ljcoomber.seamframework.org.coomber.org]

So; what worries me is what this fourth project required for JBoss Tools is?

The fourth project is for testing - no need to worry :-)