172246 – Automatic Updates for 3.2.1 not Successful with OSX

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 172246 - Automatic Updates for 3.2.1 not Successful with OSX

Summary: Automatic Updates for 3.2.1 not Successful with OSX

Status:	RESOLVED DUPLICATE of bug 167016

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Update (deprecated - use Eclipse>Equinox>p2) (show other bugs)
Version:	3.2.1
Hardware:	Macintosh Mac OS X - Carbon (unsup.)

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-Update-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2007-01-30 18:10 EST by Larry D. Wilson
Modified:	2007-01-31 09:37 EST (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Larry D. Wilson

2007-01-30 18:10:04 EST

I'm running OSX 10.4.8 on a PowerBookG4, and Java 1.5.0_06.

After I upgraded (reinstalled actually) Eclipse 3.2.1, the Update Manager seeks new updates, like it should:

Automatic Updates
New updates are available and downloaded. Do you want to review and install them now? [No] [Yes]

However, after installing these, and then restarting Eclipse, I get asked the same question - that new updates are available - even though Help -> Software Updates -> Manage Configuration (then View Installation History) displays success.

Something obviously isn't getting updated properly. I've run Disk Utility | Repair Permissions just to be safe with no change in behavior.

The Eclipse Project Updates
Eclipse 3.2.1
Eclipse Project SDK 3.2.1.r321_v20060801-tQw49KnTArT0FZ

Comment 1 Alex Blewitt

2007-01-31 06:09:47 EST

IIRC this has been reported before on 3.2.1 -- the update to 3.2.2 (when it's out) should solve it.

This can probably be closed dup of bug 167016

Alex.

Comment 2 DJ Houghton

2007-01-31 09:37:20 EST


*** This bug has been marked as a duplicate of bug 167016 ***