[news.eclipse.tools.pdt] Re: How to keep an all-in-one up to date?

[Nick Boldt <nickboldt+eclipse+newsgroup@xxxxxxxxx>]

/me looks at screnshot

Ah, I see. The issue here is that the *feature* is not new, but (maybe) 
some of the underlying plugins are.

I suspect the best workaround here (for you) is to uninstall the older 
PDT feature, restart, then install the newer one.

For the PDT devs, the solution is to commit a change to their features 
(even a no-op one) more often so that the change will be tagged, the map 
file will be updated and thus the version on the feature will be 
incremented so early adopters can update more regularly.

Nick

sNop wrote:
> Nick Boldt napsal(a):
> > > But I have problem when i want to update M2.0.1 throught update
> > > manager(from local or
> > > remote update site), because M have the same id number, simply eclipse
> > > tells me that pdt
> > > is still installed.
> > If the build ID is the same, so are the bits. You'll need a newer build.
>
> But how can i update PDT 2.0.0.v20081229-1135 (which is in stable all-in-one packege) to
> the latest PDT 2.0.1 M200901150831(which have the same id of package so PDT
> 2.0.0.v20081229-1135) throught Ganymede update manager ?
>
> I have attached picture, which everythink describe:
> http://img231.imageshack.us/img231/5880/updateproblemqb0.jpg
>
> > > Do you know about this bug, i don't know if there is tha same problem
> > > with I or N builds
> > I and N builds are for PDT 2.1.
> > M builds are for PDT 2.0.1.
>
> aha

--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb