Re: Announcement iSphere 2.9.4.r and 3.0.0.b007

Same here.

Met vriendelijke groeten / Best regards,

Peter Colpaert
Software Engineer – BG Home PLM Development Team Lead
R&D IT

Philips Innovative Applications N.V, Steenweg op Gierle 417, Building B1-17, B-2300 Turnhout, Belgium
Email: Peter.Colpaert@xxxxxxxxxxx

Home Office on Wednesdays and Fridays



-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Bailey
Sent: maandag 16 januari 2017 10:55
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Announcement iSphere 2.9.4.r and 3.0.0.b007

Hi,

I tried to upgrade iSphere this morning and I am now getting the CertPathValidatorException errors reported on this list in November last year.

Subject: Re: Having trouble installing iSphere
From: Tools/400 <thomas.raddatz@xxxxxxxxxxx>
Date: Mon, 28 Nov 2016 18:05:30 +0100

________________________________
Just for the records. The CheckTrust error does not only happen for
the iSphere plug-in:

http://stackoverflow.com/questions/25094583/error-when-try-install-plu
gin

https://bugs.eclipse.org/bugs/show_bug.cgi?id=434563

It seems to be one of the mystical Eclipse errors.

Thomas.

I've renamed every artifacts.xml file I could find under the SDP and SDPShared folders, started RDi as admin and with the -clean option, yet I am still unable to update the plugin (same security error). I tried on a completely unrelated installation and I am getting the same error there as well. Are there any more pointers for what I can do? Currently iSphere is uninstalled from one installation (another attempt to get past the problem) and I'm already missing it! I don't want to download the zip file from sourceforge if I can avoid it...


-Paul.



On 14 January 2017 at 15:03, Tools/400 <thomas.raddatz@xxxxxxxxxxx> wrote:

Hi Folks,

I want to let you know, that iSphere 2.9.4 and 3.0.0.b007 is available now.

Users of 2.9.3 and encouraged to update to 2.9.4, because I fixed a
CCSID problem when using "Copy Members" to copy members between
connections.

Nothing else has been changed in 2.9.4.

This is what we fixed and added to 3.0.0.b007 since 3.0.0.b006:

• Fixed CCSID problem when copying members between connections.
• Added option to select a RSE filter, when using the global iSphere
Source File Search (CTRL+H).

The "Target" radio buttons on the "iSphere Source File Search" dialog
work a bit different as they usually do. The "Filter" and "Member"
radio buttons are automatically selected, when one of the associated
fields are entered. They are used as indicators for what selection is
passed to the search engine.

I am not yet sure whether or not that was a good idea, so please let
me know your experiences.

Thank you Vern, for that great idea of the filter option.

Regards,

Thomas.

--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & 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 Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.

________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.