|
>I think that the issue is that there is difference between the installation >of the plugins themselves and the workspaces that are using them. Should >you be able to completely uninstall a plugin in one workspace when that >will then impact the others? I imagine that is why they just allow you to >disable the plugins. How about a warning window asking me if I really want to uninstall? Is the alternative (searching through directories with Explore and deleting files) any safer? However, if plugin vendors were required to use installation wizards that would allow uninstalls as you mention, that would resolve my concerns. >I am not sure what repairing a plugin means or would do. When I deleted the plugin from the /IBM/WebSphere Studio/Site Developer/eclipse/plugins directory, the Install/Update perspective gave me a button that said repair. This button was located where you would normally see the install button for a new or upgraded plugin. When I clicked the install, it reinstalled the plugin. Repair = reinstall in this situation. Thanks, Kelly -----Original Message----- From: Mark Phippard [mailto:MarkP@xxxxxxxxxxxxxxx] Sent: Thursday, January 15, 2004 9:08 AM To: Websphere Development Studio Client for iSeries Subject: RE: [WDSCI-L] Help for uninstalling a plug-in I think that the issue is that there is difference between the installation of the plugins themselves and the workspaces that are using them. Should you be able to completely uninstall a plugin in one workspace when that will then impact the others? I imagine that is why they just allow you to disable the plugins. I am not sure what repairing a plugin means or would do. If your vendor wanted you to do this, they probably should have issued a newer version and allowed you to install it. In general, the plugins themselves cannot be altered in any way so there should be no need to repair them. Anything that is "volatile" related to the plugin is stored in the workspace so changing the plugin code is not typically going to resolve a problem. I think it could be better. The Ready for WebSphere Studio validation program adds a number of requirements on vendors in this area that go above and beyond what you can do in Eclipse. Plugins pretty much have to be installed with a typical Windows install program in order to meet the validation requirements and those requirements also include providing an uninstall option. I think the issue from the Eclipse point of view, is that these requirements added by RFWS are platform-specific and cannot be handled by Eclipse itself. To "'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx> cc bcc Subject RE: [WDSCI-L] Help for uninstalling a plug-in Kelly Cookson <KCookson@xxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 01/15/2004 07:47 AM CST <HR><font size=-1>Please respond to Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx></font><HR> <font size=-1></font> Then this is one thing I don't like about Eclipse/WDSCi. Disabling a feature is not enough. We should be able to request features be removed or repaired. It seems kind of strange to have a plugin-based architecture and then have no formal way to remove or request repairs on plugins. Thanks, Kelly -----Original Message----- From: Mark Phippard [mailto:MarkP@xxxxxxxxxxxxxxx] Sent: Wednesday, January 14, 2004 5:49 PM To: Websphere Development Studio Client for iSeries Subject: RE: [WDSCI-L] Help for uninstalling a plug-in There is no formal uninstall process in general, however if you physically uninstall then it is smart enough the next time you start to make the necessary changes. For example, your vendor could have provided a Windows installer/uninstaller that might have done this. In general, the proper way to package and distribute a plugin is by also creating a "feature". When there is a feature present, it is possible to then manually disable the feature via the Install/Update "Configurations" view. This does not uninstall the plugin, it disables it in your workspace. I imagine there are open bugs for this in Eclipse.org, it probably just isn't high priority. To "'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx> cc bcc Subject RE: [WDSCI-L] Help for uninstalling a plug-in Kelly Cookson <KCookson@xxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 01/14/2004 04:23 PM CST <HR><font size=-1>Please respond to Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx></font><HR> <font size=-1></font> Okay, I found the plugin in the IBM/WebSphere Studio/Site Developer/v5.1/eclipse/plugins directory. I right-clicked and deleted it. I then closed and restarted WDSCi. This let me take an option to "repair" the plugin. So I was able to get a fresh install. But what an *ugly* way to handle this situation. And I still don't know how to permanently uninstall a plugin. Thanks, Kelly -----Original Message----- From: Kelly Cookson [mailto:KCookson@xxxxxxxxxxxx] Sent: Wednesday, January 14, 2004 4:06 PM To: Websphere Development Studio Client for iSeries Subject: [WDSCI-L] Help for uninstalling a plug-in I've looked through the WDSCi help and searched Google but have not found clear, detailed instructions on how to uninstall a plugin. I'm having trouble with a plugin and the vendor has asked me to "remove it from WDSCi completely" and reinstall it. I don't have a clue how to ensure it has been removed completely. How do I uninstall/remove a plugin? Thanks, Kelly _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
