Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 241304 - Software Update either should accept URL, or do not add into list.
Summary: Software Update either should accept URL, or do not add into list.
Status: RESOLVED DUPLICATE of bug 204184
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL: http://update.aptana.com/update/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-17 14:46 EDT by annoynimouse CLA
Modified: 2008-07-21 00:42 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description annoynimouse CLA 2008-07-17 14:46:41 EDT
If to add URL like http://update.aptana.com/update/ - Eclipse will cry 'it 
is not update site!" but still will add it to the list. 

IMHO if Eclipse is 
so sure to make such a strong statement, it is not expected to add not-update-site to the list. Maybe it is not to be added at all, maybe only after user prompt "i don't think it is an update site and it would do any good to put it in the list. Do you insist to keep it the the list? yes|no" 

Current behaviour seems to me inconsistent - we claim site is of no use, then we add it to the list nonetheless to have nothing good of it.

http://www.eclipsezone.com/eclipse/forums/t111929.html
Comment 1 Susan McCourt CLA 2008-07-21 00:42:37 EDT
In p2 we differentiate between adding and loading a site (loading being the potentially slow part, depending on the site, network, proxies, firewalls, etc.).  Therefore we cannot synchronously validate site content, we can only validate that the URL is valid.  

We add the site and the first time it is loaded,  we find any content-related issues with it.  This is the same timing as update 3.3 and previously (we tried to do better in bug #204184 and then backed out due to the same performance problems).



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