Does the seam/hibernate/AS tooling get "in your way" somehow ?
They should just be dormant if you don't use them.
Just trying to understand if the problem is beyond "it takes up some disk space"
since if there are a problem beyond that we will increase the priority on this.
I've installed it from a release candidate of 3.2 and I was surprised to discover that it had installed a new JSP editor, which was even slower than the standard editor from WTP.
I just want to avoid that...
In fact.. the only reason I want the portlet plugin is because it delivers the DTDs used by the JBoss Portal and the XML editor from WTP doesn't try to download them every time I open one of the configuration files specific to JBoss Portal.
even slower - that sounds bad
You can change the editor by using Open With to use the one you want by default.
If that is the only reason you can just go configure those in the XCatalog of your eclipse preferences
You can set the default editor for JSP files using Window>Preferences>General>Editors>File Associations.
It took me a few months to discover https://bugs.eclipse.org/bugs/show_bug.cgi?id=321602
Yes, I know I can change the default editor, but it seemed odd that the 3.1 version didn't have these dependencies and now 3.2 does.
Does it really use something from these new added dependencies?
JBoss Portlet feature always required those dependencies. The problem was happening when the user created a portlet. Because of that the seam dependency was added to the portlet feature within JBIDE-7293.
The next JBoss Tools version will have the JBoss Portlet Core feature that won't require Seam and the JBoss Portlet Seam feature that will require Seam.