Re: [buckminster-dev] Update Manager for buckminster workaround or doesn

["jaikumar" <jaikumar.sharma@xxxxxxxxx>]

Thanks Ken1,
Eclipse Update Manager worked, I only had to supply my proxy server IP  and 
port, and everything worked fine. First materialization also worked.

Thanks again for your help!

Regards


"ken1 (Kenneth Ölwing)" <kenneth@xxxxxxxxx> wrote in message 
news:eb87ij$7as$1@xxxxxxxxxxxxxxxxx...
> RE: [buckminster-dev] Update Manager for buckminster workaround or doesnot 
> work at all ?>It is not possible to install Buckminster with Eclipse 
> Update Manager, I
>>believe there are reasons due to organization firewall.
>
> Yes, that sounds likely. You then have problems connecting to, at a 
> minimum, any update site hosted at Eclipse? Check with your IT staff and 
> see if your organization has a proxy server to the internet...that sounds 
> like the most likely cause to me (and as noted, generally easy to adjust 
> for).
>
>>Instead, I downloaded "Site Archive" -
>>buckminster.archivedsite-1.0.0.v20060725.zip and extracted the same to
>>Eclipse installation.
>
> Anyway, this is a good workaround. Be aware that there is a later build, 
> 20060803 that corrects a problem that makes it difficult to build in many 
> instances (corrupt class file). I've also identified and fixed a couple of 
> NPE's in CVS, but haven't been able to make a build yet...
>
>>Would this also work same as IDE packaging ? Or any other means to get
>>it working ?
>
> I'm not 100% sure what you mean. So, I'll just explain briefly about the 
> packagings and hope that clears up some confusion...
>
> The 'archivedsite' zip file is just the ordinary update site packaged as a 
> zip. So, you can use the update manager and use the 'New Archived Site...' 
> button to point to it. From that point on things will work the same.
>
> The other packaging is the product build zip - that however is a very 
> different animal. Basically a packaged core Eclipse/OSGi runtime with some 
> basic Buckminster features. This is the headless stuff - it can be 
> extended with features using the same underlying 'Eclipse Update Manager' 
> API, but has to be accessed by command line (the 'install' command). It 
> can also use either the real update site or the archivedsite, as needed.
>
> Hope this answers your questions, please come back if I completely 
> misunderstood you :-)
>
>>Thanks for your help!
>
> You're welcome :-)
>
> ken1
>