adding plugins (was: Re: Q) eclipse 3.2 (Callisto))

[Ronald Klop]

On Tue, 29 Aug 2006 07:42:00 +0200, Norberto Meijome <freebsd at meijome.net>  
wrote:

> On Mon, 28 Aug 2006 22:22:36 -0700
> Sean McNeil <sean at mcneil.com> wrote:
>
>> The big problem that I see is there are a number of plugins that have
>> decayed and no longer install.  At lease I've seen posts to eclipse@
>> about this.  Perhaps they have been updated by now, but what I saw was
>> that the download was no longer valid.
>>
>
> hmm not sure.. i've installed several over the last couple of weeks and  
> there
> are all still valid.
>
>> If this is the case, then just update them all to 3.2 or compatible. If
>> there is enough interest, then make an eclipse31.  But it seems like it
>> will just get harder to maintain the older version as time marches on.
>
> sure , i was trying to avoid the case where we push eclipse to 3.2, but  
> there
> isn't enough push/ time to upgrade the plugins fast enough. I can easily
> install from the update manager....so I guess everyone else can too (as  
> long as
> you remember to sudo eclipse first ;) ).... so i guess it isn't that
> important :)
> B

In stead of 'sudo eclipse' you can also add an 'extension location' in  
your home-directory and tell eclipse to install plugins there. This works  
very well for 100% Java plugins. A lot of the Callisto plugins can also be  
installed (and used) this way by non-root users.

Ronald.

-- 
  Ronald Klop
  Amsterdam, The Netherlands