| Select Required Projects in Find Updates [message #243104] |
Fri, 14 December 2007 10:30  |
Eclipse User |
|
|
|
When I click the Select Required Projects field in the Find Updates menu,
it does nothing when the required project is in an update site that wasn't
initially selected in the list of update sites to search for new features
- is this expected behavior?
Even when I do include the necessary update site in the list, Select
Required Projects does nothing unless you first maximize the menu for that
update site. It seems that Eclipse doesn't search update sites selected
that aren't first maximized - this certainly isn't expected behavior, is
it?
If so, I guess the Select Required Projects function is somewhat less
valuable than I thought - because not only do you need to know which of
the update sites in your list of update sites to search from the initial
menu, but you also need to maximize each one.
I hoped when you click Select Required Projects it would search every
update site you've specified in Eclipse automatically and bring that in.
Is the above behavior the case with everyone, or am I doing something
wrong? (I'm using Eclipse 3.3.1.1).
Thanks.
|
|
|
| Re: Select Required Projects in Find Updates [message #243150 is a reply to message #243104] |
Fri, 14 December 2007 13:31  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
VK wrote:
> When I click the Select Required Projects field in the Find Updates
> menu, it does nothing when the required project is in an update site
> that wasn't initially selected in the list of update sites to search for
> new features - is this expected behavior?
Yes, I think so. If Eclipse were to try to search all "known" update
sites it would be very slow, and there could be conflicts when multiple
sites declare the same plugins.
> Even when I do include the necessary update site in the list, Select
> Required Projects does nothing unless you first maximize the menu for
> that update site. It seems that Eclipse doesn't search update sites
> selected that aren't first maximized - this certainly isn't expected
> behavior, is it?
That does sound like a bug; it is at least surprising. I can't try to
reproduce it, though, because my current Eclipse installation has almost
all of the "core" Europa features installed already ;-)
You are welcome to enter a bug report about it - that way someone will
be "forced" to confirm, explain, or deny its behavior.
Hope this helps,
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.34692 seconds
Home