|
(By "uncomfortable", I think Thomas means the process I outlined - below
- is a little more involved than simply pointing to a web address to
download and install.)
I would respectfully suggest that the steps I follow aren't at all
arduous or complicated and take an extra minute or two to complete. The
advantage is having to download the .ZIP file just the once, handy if
iSphere is to be deployed on multiple devices.
And it works.
HTH,
Brian.
On 25/04/2021 17:48, Alan Shore via WDSCI-L wrote:
Uncomfortable?
In what way?
Maybe I might wait a while
I'm nearing the end of a highly visible project
Don't want to do anything thatan screw things up for me
That's one of the reasons I haven't opted my ACS
Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone
-------- Original message --------
From: Tools/400 <thomas.raddatz@xxxxxxxxxxx<mailto:thomas.raddatz@xxxxxxxxxxx>>
Date: 4/25/21 12:18 (GMT-05:00)
To: wdsci-l@xxxxxxxxxxxxxxxxxx<mailto:wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] [EXTERNAL] iSphere 4.0.0.r released
That is the most reliable approach available. But it is also the most
uncomfortable approach.
Thomas.
Am 25.04.2021 um 16:58 schrieb Brian Parkins:
FWIW, I >always< use Check For Updates. Never fails. On Windows I have a--
standard folder (C:\RDi Plugins\iSphere) from where the plug-in was
initially unzipped and installed. The procedure I follow is:
- Download the .ZIP file
- Clear existing standard folder
- Unzip new version in standard folder
- Start RDi
- Use HELP > CHECK FOR UPDATES
Invariably the newer version of iSphere is picked up: just follow the
prompts.
HTH,
Brian.
On 25/04/2021 10:40, Tools/400 wrote:
Allan,
Did you already told us what version of RDi you use? I could not find
that information. I assume that you use 6.6 or higher so that
validating the certificate chain should work. It does not work any
longer for RDP 8.0.
When I create a new release I test the repository by updating iSphere
via:
* Install New Software
* Eclipse Marketplace
I never use "Update Software".
Thomas.
Am 24.04.2021 um 21:26 schrieb Alan Shore via WDSCI-L:
Thanks Paul
I will try thato tomorrow
Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone
-------- Original message --------
From: Paul Therrien <paultherrien@xxxxxxxxxxxxxxxxxx<mailto:paultherrien@xxxxxxxxxxxxxxxxxx>>
Date: 4/24/21 09:42 (GMT-05:00)
To: 'Rational Developer for IBM i' <wdsci-l@xxxxxxxxxxxxxxxxxx<mailto:wdsci-l@xxxxxxxxxxxxxxxxxx>>
Subject: Re: [WDSCI-L] [EXTERNAL] iSphere 4.0.0.r released
I updated iSphere at around 4pm New York time on 4/23 with no issues.
In RDI I did an install software and pointed to the iSphere
repository -
http://isphere.sourceforge.net/eclipse/rdi8.0/<http://isphere.sourceforge.net/eclipse/rdi8.0><http://isphere.sourceforge.net/eclipse/rdi8.0<http://isphere.sourceforge.net/eclipse/rdi8.0>><http://isphere.sourceforge.net/eclipse/rdi8.0<http://isphere.sourceforge.net/eclipse/rdi8.0><http://isphere.sourceforge.net/eclipse/rdi8.0<http://isphere.sourceforge.net/eclipse/rdi8.0>>>
Downloaded and installed with no issue.
Note: I use the 'Install New Software' option instead of the 'Check
for Updates' function.
This has always worked for me.
Paul
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>> On Behalf Of
Tools/400
Sent: Friday, April 23, 2021 1:57 PM
To: wdsci-l@xxxxxxxxxxxxxxxxxx<mailto:wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] [EXTERNAL] iSphere 4.0.0.r released
I have no idea why that happens. It might be a problem at SourceForge
or a caching problem somewhere else.
BTW, when I mentioned earlier in this thread that I successfully
installed iSphere 4.0.1, then I did that with RDi 9.6.
I cannot update RDP 8.0 for a long time, because of the following
error:
Unable to read repository at
http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml<http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml><http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml<http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml>><http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml<http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml><http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml<http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml>>>.
Unable to read repository at
http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml<http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml><http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml<http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml>><http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml<http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml><http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml<http://isphere.sourceforge.net/eclipse/rdi8.0/site.xml>>>.
Received fatal alert: protocol_version
I assume that SourceForge changed the TLS version to a newer version,
that is not supported by the Java runtime included in RDP 8.0.
For RDi 9.6 users I suggest to close and restart RDi or wait for the
next day.
Thomas.
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx<mailto:WDSCI-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l<https://lists.midrange.com/mailman/listinfo/wdsci-l><https://lists.midrange.com/mailman/listinfo/wdsci-l<https://lists.midrange.com/mailman/listinfo/wdsci-l>>
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx<mailto:WDSCI-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l<https://archive.midrange.com/wdsci-l><https://archive.midrange.com/wdsci-l<https://archive.midrange.com/wdsci-l>>.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com<https://amazon.midrange.com><https://amazon.midrange.com<https://amazon.midrange.com>>
The Nature’s Bounty Co. is now The Bountiful Company! Our email
address will be changing from @nbty.com to @bountifulcompany.com.
Please update your email address book so that important communications
are not interrupted.
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
