[wtp-releng] Including the o.e.wst.jsdt.debug.rhino.ui plug-in to WTP p2

[Victor Rubezhny <vrubezhny@xxxxxxxxxx>]

Hi!

In order to make WST free of any dependencies to JDT we've excluded 
o.e.wst.jsdt.debug.rhino.ui plug-in (as the only plug-in that depends in 
JDT) from JSDT-feature (See: 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=410982 - 
o.e.wst.jsdt.debug.rhino.ui has dependencies to JDT).

This change, however, moved Rhino Debug UI plug-in completely out of WTP 
repository. So, the clients that need to launch/debug their JavaScripts 
using Rhino have lost such a feature. So, we're looking for a solution 
on how to provide users with the possibility to install Rhino Debug UI 
plug-in from WTP or other repo.

I've opened Bug #434664 
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=434664 - 
o.e.wst.jsdt.debug.rhino.ui should be added to JBDS Site) and provided a 
patch in order to include Rhino Debug UI plug-in into JBDS Update Site 
(as an optional plug-in) - and I need this fix to be reviewed with WTP 
Releng team.

Also, I'm not sure that adding the plug-in into JBDS Site will solve the 
problem of availability of the plug-in for WTP users, so I'd like to ask 
WTP Releng team on what I (we) should do in order to provide the users 
with the possibility to install o.e.wst.jsdt.debug.rhino.ui plug-in?

I'd like to think that removing the plug-in (because of its dependency 
to JDT) from JSDT Feature is the only timely solution, and me (or some 
other contributor) will be able to solve JDT-dependency problem for this 
plug-in. But this unlikely to happen for WTP 3.6, so, IMHO, we have to 
make Rhino Debug UI plug-in available somehow from outside of WST for 
WTP 3.6.

Thanks in advance,
Victor Rubezhny