Re: Need help with iSphere ticket #129

[Brian Parkins <goodprophet.bp@xxxxxxxxx>]

I follow very similar steps, Thomas and add a "refinement".

1). I have a single folder, say ISPHERE that contains the (existing) 
unzipped plug-in files; this is the  Local Update Site
2). Download the new version zip to a "repository" (backup) folder
3). Delete all the files from the ISPHERE folder
4). Unzip the new version from the repository to ISPHERE
5). Start RDi
6). Check for updates

(In fact, RDi will detect the new iSphere version in Step 5.)

So I only ever have a single, Local Update Site - which always contains 
the current version. Never fails. As always, thank you for all the work 
you put in, Thomas.

Brian.


On 03/07/2022 17:42, Tools/400 wrote:
> Hi Brian,
>
> You are correct. Using the zip file is the most reliable method. 
> Another option is unzipping the zip file into a local folder. This way 
> you have a local update site with a stable name. That is how I share 
> iSphere with my colleagues:
>
> 1) Download the zip.
> 2) Extract the zip into an empty folder on a server share.
> 3) Add that folder as a local update site.
>
> Work perfectly fine.
>
> Thomas.
>
> Am 28.06.2022 um 15:57 schrieb Brian Parkins:
> > Matt, have you tried downloading the ZIP archive from here:
> >
> > https://sourceforge.net/projects/isphere/
> >
> > and installing locally from this? My preferred method and works every 
> > time.
> >
> > HTH,
> > Brian.
> >
> > On 28/06/2022 13:01, Matt Qualls wrote:
> > > Hi Thomas,
> > >
> > > It won't install from "Check for Updates".  I get the encountered a 
> > > problem error.  For me, I found that going through the Eclipse 
> > > Marketplace is the only method that works for these 3 machines.  
> > > Perhaps there's an issue on the RDi or Eclipse side.  iSphere is the 
> > > only plug-in that I have installed.  I've been using  IBM IDEs since 
> > > CODE/400 on OS/2 WARP.  I've learned to adjust and move on.  As long 
> > > as I can update it and use it, I'm happy.
> > >
> > > Thank you for your and your contributors hard work on this product.
> > >
> > > Matt