RE: Removing a plug-in -- WDSCI-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: [WDSCI-L] Removing a plug-in
From: J.Beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx
Date: Tue, 5 Oct 2004 15:04:19 +0200
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Websphere Development Studio Client for iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

Kelly,

It is not WDSc-specific; the whole plugin mechanism is Eclipse.

Joep Beckeringh


>That is my understanding as well. 
>
>I think this is one of the times when the cracks in the WDSCi-on-Eclipse
>strategy shows through. IBM doesn't have to deal with this issue because
>they can point to Eclipse and say it's their problem. Eclipse is not
>obligated in any way to WDSCi users, so they can say they have more
>important things to do. Bottom line, WDSCi users are left dealing with a
>product deficiency. 
>
>Kelly

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.