| Unreachable features not displayed? [message #276985] |
Thu, 02 December 2004 12:29  |
Eclipse User |
|
|
|
Originally posted by: jimhsu.us.nospam.ibm.com
As a suggested enhancement, it would be helpful to display unreachable
features in the install UI.
Here is an example which illustrates the problem. Assume my.server.com is
running, but unavailable.server.com is temporarily down.
<feature url="http://my.server.com/features/myfeature_1.0.0.jar"
id="my.feature" version="1.0.0">
<category name="myFeature"/>
</feature>
<feature
url=" http://unavailable.server.com/features/mydependency_1.0.0.ja r"
id="my.dependency" version="1.0.0">
<category name="myDependency"/>
</feature>
<archive path="plugins/mydependency_1.0.0.jar"
url=" http://unavailable.server.com/plugins/mydependency_1.0.0.jar"/>
In this situation, myFeature is found, but it will complain about an
update conflict, namely that it requires myDependency.
However, the Eclipse error does not mention that it could not connect to
unavailable.server.com. From the user's perspective, they have no idea to
try it later. They may not even be aware of the missing dependency
because unreachable features do not show up in the UI list.
A better solution would be to display unreachable features with a red X,
and the error details should indicate why it is unreachable. (Cannot
connect to server, etc.)
Should I enter a bug or feature request on this? (If so, which is it, bug
or feature request? Also, what category is it? Platform?)
|
|
|
| Re: Unreachable features not displayed? [message #276991 is a reply to message #276985] |
Thu, 02 December 2004 14:10  |
| Eclipse User |
|
|
|
Originally posted by: dorian.birsan.net
Jim,
Open a feature request on Platform Update.
"Jim Hsu" <jimhsu@us.nospam.ibm.com> wrote in message
news:conje0$69f$1@www.eclipse.org...
> As a suggested enhancement, it would be helpful to display unreachable
> features in the install UI.
>
> Here is an example which illustrates the problem. Assume my.server.com is
> running, but unavailable.server.com is temporarily down.
>
> <feature url="http://my.server.com/features/myfeature_1.0.0.jar"
> id="my.feature" version="1.0.0">
> <category name="myFeature"/>
> </feature>
>
> <feature
> url=" http://unavailable.server.com/features/mydependency_1.0.0.ja r"
> id="my.dependency" version="1.0.0">
> <category name="myDependency"/>
> </feature>
>
> <archive path="plugins/mydependency_1.0.0.jar"
> url=" http://unavailable.server.com/plugins/mydependency_1.0.0.jar"/>
>
> In this situation, myFeature is found, but it will complain about an
> update conflict, namely that it requires myDependency.
>
> However, the Eclipse error does not mention that it could not connect to
> unavailable.server.com. From the user's perspective, they have no idea to
> try it later. They may not even be aware of the missing dependency
> because unreachable features do not show up in the UI list.
>
> A better solution would be to display unreachable features with a red X,
> and the error details should indicate why it is unreachable. (Cannot
> connect to server, etc.)
>
> Should I enter a bug or feature request on this? (If so, which is it, bug
> or feature request? Also, what category is it? Platform?)
>
|
|
|
Powered by
FUDForum. Page generated in 0.30970 seconds
Home