Community
Participate
Working Groups
Assuming RFE bug 154100 complete with proxy management and Authenticator support continues unabated into Eclipse 3.3, we will need to remove the org.eclipse.wst.internet.proxy plugin.
Targetted to WTP 2.0 M6. Added Michael and David as presumed interested parties.
Peter, none of the Web service plugins [1] import org.eclipse.wst.internet.proxy, therefore, removing the plugin should not cause any specific damage to the Web services platform. Plugin org.eclipse.wst.ws.explorer refers directly to the JDK system properties. Since the properties should be initialized long before the WSE gets launched by a user, the WSE shouldn't feel a thing, however, please do test it after you've removed org.eclipse.wst.internet.proxy. [1] Plugins searched org.eclipse.jst.ws org.eclipse.jst.ws.axis.consumption.core org.eclipse.jst.ws.axis.consumption.ui org.eclipse.jst.ws.axis.creation.ui org.eclipse.jst.ws.consumption org.eclipse.jst.ws.consumption.ui org.eclipse.jst.ws.creation.ejb.ui org.eclipse.jst.ws.creation.ui org.eclipse.jst.ws.uddiregistry org.eclipse.jst.ws.ui org.eclipse.wst.command.env org.eclipse.wst.command.env.core org.eclipse.wst.command.env.ui org.eclipse.wst.common.environment org.eclipse.wst.internet.cache org.eclipse.wst.internet.proxy org.eclipse.wst.ws org.eclipse.wst.ws.explorer org.eclipse.wst.ws.parser org.eclipse.wst.ws.ui
*** Bug 178800 has been marked as a duplicate of this bug. ***
The fix for this defect has been completed. The following was changed: 1) org.eclipse.wst.common_ui.feature was updated to remove entries for: - org.eclipse.wst.internet.proxy - org.eclipse.wst.internet.proxy.infopop The changes to this feature were committed and released under version v200703221921 2) org.eclipse.wst.internet.proxy was removed from the wst-common-ui.map file. 3) org.eclipse.wst.internet.proxy.infopop was removed from the wst-doc.map file.
What to do with the component.xml file in org.eclipse.wst.internet.monitor.core? Did this plugin have an API that we need to be concerned about? That is, concerned about providing at least migration instructions, if not leave some "deprecated" version of the API's in place, to allow people to migrate slowly? Did you check the adopter scan data? I believe too, that JSF pre-req'd this bundle. Not sure how it was used, of if/when they have migrated.
Also, there will be some documentation implications for this change. Some doc removed from WTP, and some doc added to the platform. Kate, adding you as CC so you can fix WTP side, and/or coordinate platform side, if they need it. John, I added you as CC so you can coordinate/update any "help for old friends" etc.
Plugin had no official API. FWIW, I can easily remove it from the component.xml once Peter/Chris have confirmed that it had no internal API users or respond to David's concerns about migration and deprecation.
I have entered bug 179295 to document the proxy support in Platform. If someone from WTP could attach the current doc from WTP, that would save me a bit of work.
The org.eclipse.wst.internet.proxy plugin did have a few of internal classes( 12 to be exact). None of these classes were part of an internal api.(ie. all were implmentation classes. Unfortunately, the manifest file did export these classes as internal, so it is possible that someone could have used them. That said, since these really are internal implementation classes I would recommend that we continue to just delete this plugin. If some adopter really is using one of these internal classes they can always make a copy of them from the WTP 1.5 stream, since the number of classes is extremely small and self contained. I searched the adopter usage xml files and didn't find any references to the org.eclipse.wst.internet.proxy plugin, so at least registered adopters shouldn't be affected by this change. Therefore, I recommend that Tim should remove this plugin from the component.xml file.
Change to component.xml released to 2.0 builds.
Re-resolved as fixed based on changes having been made by Peter (comment 4) and Tim (command 10).
We are closing down the WTP 2.0 release pretty soon, please verify these defects with the latest WTP 2.0 build. The WTP 2.0 RC2 driver is available at: http://download.eclipse.org/webtools/downloads/drops/R2.0/S-2.0RC2-200706050057/
Verified by inspection of WTP 2.0 RC2 SDK plugins directory. Closed.
New Gerrit change created: https://git.eclipse.org/r/108190
