JBoss Tools candidate release

[maxandersen]

Thought you might be interested in http://in.relation.to/Bloggers/JBossTools2ReleaseCandidate

[pmuir]

http://in.relation.to/Bloggers/JBossTools2ReleaseCandidate

Nice work Max :)

[nickarls]

Nice work!

But could you set something straight for me: Is it called "JBoss Tools" or "Red Hat Developer Studio"? Are the same? Is RHDS the successor of JT? Cousins? Roommates?

[maxandersen]

JBoss Tools are the opensource eclipse plugins we develop for JBoss releated tech (hereunder the Seam ones)

RHDS is a full bundle of jboss tools, jboss EAP, eclipse, 3rd party plugins and RHEL available under subscription when RHDS goes final - see more at redhat.com/developers/rhds

[samdoyle]

Why does Red Hat Developer Studio not allow you to create a Seam project if you are using Glassfish for your server instance?

Does this mean I can't use RHDS if I am using Glassfish?

[nickarls]

"Add ICEFaces nature" would be nice (or as an option in the Seam project creation process). I didn't see it in the JIRA, do you have something planned for it in the future?

[maxandersen]

nickarls:
ICEFaces Nature ?! What should that do ?

If you talk about adding icefaces libraries then that will be solvable when bring back the "Add capabilities" feature (which also should help us work with ant/maven/ivy builds)

But the other part is that the seamgen and all other templates needs to be adjusted (and tested) for icefaces compability.....(there is some work in the seam-gen directory but not sure how easy that is to utilize for us)

Wanna contribute ?

btw. it is Eclipse and we don't depend on any richfaces.jar etc. in the project so you can just add the jars and have fun ;)

samdoyle:
You can use JBossTools/RHDS with Glassfish - you just need to use the Glassfish WTP adapter. the only that won't work is the Seam Wizard Project creation since Glassfish WTP adapter is not listed as compatible with jst.seam. Note: if you have an existing project you can use the seam related features like jsf, el code completion, seam views etc. without any issues.

[nickarls]

Well, it would automagically add the required libraries, modify web.xml and components.xml and generally produce the same thing as through seam-gen.

Contribute? What, no free lunch!?1 ;-)

[maxandersen]

nickarls:
Nope - no freebies around here ;)

btw. the reason I put ?! next to nature is that a "nature" is what is used for something that needs to hook into the compilation/verification/project lifecycle which was not what you wanted ;)

About add libraries, modify web.xml (and possibly components.xml) then that is exactly what the "Add capabilities" is about (and for any other library in general) - we just couldn't make that play well enough with the ant/maven/ivy crowds to include it for GA; we will get it in one of the 2.x releases ;)

Handle the seam-gen templates will be much much harder since these templates are not trivial and to keep them in sync with two or more different componentsets is definitly not going to happen without some hefty community contributions (and somehow find a way to not require us to change somethng in the eclipse tooling everytime a new change is made)

[samdoyle]

Thanks for getting back to me Max,

Yes, this is what I tried to do, I installed the Glassfish adapter and tried to create a new Seam based project using it. I'll try the other route you mentioned. Could it be made compatible so that it would work with new Seam projects? I'm not sure what the issues are involved in doing this?

Am I losing anything by not being able to create a Seam Project?

Thanks, S.D.

samdoyle:
You can use JBossTools/RHDS with Glassfish - you just need to use the Glassfish WTP adapter. the only that won't work is the Seam Wizard Project creation since Glassfish WTP adapter is not listed as compatible with jst.seam. Note: if you have an existing project you can use the seam related features like jsf, el code completion, seam views etc. without any issues.

[maxandersen]

What I hope we can get pretty soon is one of two things:

1) You can select Glassfish (or any other JSF capable adapter) when creating the project and then you might have to adjust certain artifacts to work with Glassfish or whatever runtime/server you decide to use
(the related jira is http://jira.jboss.com/jira/browse/JBIDE-1320)

2) You can setup the output directories for the seam-gen specific wizards so you aren't dependent on the project being setup via the seam wizard.
(the related jira is http://jira.jboss.com/jira/browse/JBIDE-1003)

Both #1 and #2 is high on my priority list.

[maxandersen]

I forgot to answer the other two questions ;)

"Am I losing anything by not being able to create a Seam Project?"

Currently you are "only" loosing the other seam-gen based wizards; but everything else works if you just enable Seam on your project. Everything else is here seam component view, jsf visual editor, el code completion, hibernate querying etc.

"Could it be made compatible so that it would work with new Seam projects? I'm not sure what the issues are involved in doing this?" - Yes, but as far as I know the requirement right now is to list the glassfish server as "supported" under the jsf.seam facet (see http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105089#4105089)

[marx3]

i've used RHDS and when I saw it isn't free i've tried JBoss Tools. I use them in production environment.
I've downloaded WTP, JBossTools and only one plugin PropertiesEditor, nothing more.
WTP+JBossTools is totally unstable. It hangs (I can click menu etc but no action is made) and sometimes Eclipse closes without any warning or error. There is something wrong with such setup. Problem is in part with WTP, because I had similair behaviours - sudden exiting - with WTP only, and in part with JBossTools (hanging).

Now I'm back to RHDS beta - it's stable as rock.

[maxandersen]

http://blog.xam.dk/archives/79-Eclipse-The-Memory-Hog-resolved!.html

[marx3]

it seems it helped, thank you :)