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

Bug 338333

Summary: Automatic updates for Eclipse following streams
Product: [Eclipse Project] Equinox Reporter: Albert Zeyer <albzey+eclipsebugs>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: pascal, prakash, remy.suen
Version: 3.5.2   
Target Milestone: ---   
Hardware: Macintosh   
OS: Mac OS X   
Whiteboard: stalebug

Description Albert Zeyer CLA 2011-02-27 08:59:26 EST
I am missing a possibility to automatically update Eclipse. I don't want to frequently have to check the website for new updates. I want that Eclipse automatically knows what channel I am in (i.e. stable or trunk or so) and checks in that channel for new updates and automatically installs them (maybe ask me first but I would just always install it).


-- Configuration Details --
Product: Eclipse 1.2.2.20100122-1337 (org.eclipse.epp.package.java.product)
Installed Features:
 org.eclipse.platform 3.5.2.R35x_v20100210-0800-9hEiFzmFst-TiEn9hNYgDWg1XN8ulH_JvCNGB
Comment 1 Remy Suen CLA 2011-02-27 09:14:31 EST
Maybe something more appropriate for the cross projects inbox but moving to p2 first.
Comment 2 Prakash Rangaraj CLA 2011-02-27 23:51:02 EST
Albert,

        The Automatic Updates in the Preferences not working for you?
Comment 3 Albert Zeyer CLA 2011-02-28 06:34:29 EST
I have Eclipse 3.5.2 installed and I clicked on it and it didn't found out that there is a new major release. I was told in another bug report that it is also not what it is made for (it just searches in the predefined repositories which only cover 3.5.2 in that case).

But what I am actually asking for here is a function which really searches for new versions and installs them.
Comment 4 Lars Vogel CLA 2019-11-14 03:32:23 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.