[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Advice on update site problem?
|
Thanks for the explanation, Nick, this is very helpful!
We've identified one feature as missing the update URL, and added a policy
file to our update site as well.
Regards,
John Graham
Eclipse Data Tools Platform PMC Chair
Staff Software Engineer, Sybase, Inc.
http://dataplat.blogspot.com/
"Nick Boldt"
<codeslave@xxxxxx
.com> To
Sent by: "Cross project issues"
cross-project-iss <cross-project-issues-dev@eclipse.o
ues-dev-bounces@e rg>
clipse.org cc
Subject
10/04/2007 09:49 Re: [cross-project-issues-dev]
PM Advice on update site problem?
Please respond to
Cross project
issues
<cross-project-is
sues-dev@eclipse.
org>
> (1) Any ideas why the two search methods return different results? Did we
> do something wrong on our update site?
If I'm not mistaken, the difference is that one will check the update
URLs for each feature based on the information in those features'
feature.xml files. The other is not beholden to checking anything
that's already installed, and can do a full search, finding more.
Generally, the solution I've put forth to people when the 'search for
updates' fails is "don't use that, use 'search for new features'".
It's sorta the old adage of "Doctor, it hurts when I do *this*" -- "So
don't do *this*!" ;-)
Chances are there's nothing wrong with your update site, but your
features may be missing update URLs. You can force those features to
be updated regardless of what's present using a policy file.
http://wiki.eclipse.org/Testing_Pre-Release_Builds_Via_Policy_Files
Hope that helps,
--
Nick Boldt :: Release Engineer, IBM Toronto Lab
Eclipse Modeling :: http://www.eclipse.org/modeling
http://wiki.eclipse.org/index.php/User:Nickb
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev