Home » Eclipse Projects » GEF » Problem with command line update manager
| Problem with command line update manager [message #190514] |
Thu, 04 August 2005 13:08  |
 Richard Gronback
Messages: 605
Registered: July 2009 |
Senior Member |
|
|
I've tried to download GEF 3.1.0 using the following options via the command
line (standalone) update manager:
-command install -featureId org.eclipse.gef -version 3.1.0 -from http://update.eclipse.org/updates/
The update site URL, ID, and version I obtained from the GEF feature.xml
file. What I'm doing is trying to utilize update manager functionality for
installing EMF and GEF during GMF's automated build process.
When I execute this command, I get the following error:
org.eclipse.core.runtime.CoreException[0]: org.eclipse.core.runtime.CoreException[0]:
java.io.IOException: Server returned HTTP response code: "404 Not Found"
for URL: http://update.eclipse.org/updates/plugins/org.eclipse.draw2d _3.1.0.jar.
After some investigation, it seems the update manager resolves the feature's
plug-ins to a default location based on the update site root, followed by
'/plugins/<plug-in name>.<version>.jar', if it does not find a reference
to the plug-in location in the site.xml file. For GEF features, it seems
the older site.xml references the 3.0 update locations using URLs prefixed
with '3.0/' (and, this seems to be a GEF exclusive). So, the feature itself
is matched, but plug-in references are resolved as in the above, without
'3.0/' in the path, and therefore causing the 404 Not Found error.
If I use http://update.eclipse.org/updates/3.0 for the -from argument, it
works as expected. Note that the update manager works fine through the GUI,
as I suspect it is using the ../3.0/site.xml file (or is able to resolve
the correct plug-in URLs by some other means).
So, not sure if I'm missing something here, or if it's an issue with the
update manager... but it seems if the URL in the feature.xml were to point
to http://update.eclipse.org/updates/3.0 all would be well.
Thanks,
Rich
|
|
|
| Re: Problem with command line update manager [message #190553 is a reply to message #190514] |
Thu, 04 August 2005 17:23  |
Eclipse User |
|
|
|
Originally posted by: none.unknown.com
We have a bug report open to sort this out. Thanks for your explanation
about what's happening behind the scenes, Rich. The updates don't work from
the GUI either. I think you're referring to discovery, which works fine.
The update URL only comes into play when you already have an older version
installed (and select the option to search for newer versoins of already
installed plugins).
<richard.gronback@borland.com> wrote in message
news:1e24834217ff68c766eb2d217b40@news.eclipse.org...
> I've tried to download GEF 3.1.0 using the following options via the
command
> line (standalone) update manager:
>
> -command install -featureId org.eclipse.gef -version 3.1.0 -from
http://update.eclipse.org/updates/
>
> The update site URL, ID, and version I obtained from the GEF feature.xml
> file. What I'm doing is trying to utilize update manager functionality
for
> installing EMF and GEF during GMF's automated build process.
>
> When I execute this command, I get the following error:
>
> org.eclipse.core.runtime.CoreException[0]:
org.eclipse.core.runtime.CoreException[0]:
> java.io.IOException: Server returned HTTP response code: "404 Not Found"
> for URL:
http://update.eclipse.org/updates/plugins/org.eclipse.draw2d _3.1.0.jar.
>
> After some investigation, it seems the update manager resolves the
feature's
> plug-ins to a default location based on the update site root, followed by
> '/plugins/<plug-in name>.<version>.jar', if it does not find a reference
> to the plug-in location in the site.xml file. For GEF features, it seems
> the older site.xml references the 3.0 update locations using URLs prefixed
> with '3.0/' (and, this seems to be a GEF exclusive). So, the feature
itself
> is matched, but plug-in references are resolved as in the above, without
> '3.0/' in the path, and therefore causing the 404 Not Found error.
>
> If I use http://update.eclipse.org/updates/3.0 for the -from argument, it
> works as expected. Note that the update manager works fine through the
GUI,
> as I suspect it is using the ../3.0/site.xml file (or is able to resolve
> the correct plug-in URLs by some other means).
>
> So, not sure if I'm missing something here, or if it's an issue with the
> update manager... but it seems if the URL in the feature.xml were to point
> to http://update.eclipse.org/updates/3.0 all would be well.
>
> Thanks,
> Rich
>
>
|
|
|
| Re: Problem with command line update manager [message #190561 is a reply to message #190514] |
Thu, 04 August 2005 17:36 |
| Eclipse User |
|
|
|
Originally posted by: none.unknown.com
The update URL will be fixed in 3.1.1.
<richard.gronback@borland.com> wrote in message
news:1e24834217ff68c766eb2d217b40@news.eclipse.org...
> I've tried to download GEF 3.1.0 using the following options via the
command
> line (standalone) update manager:
>
> -command install -featureId org.eclipse.gef -version 3.1.0 -from
http://update.eclipse.org/updates/
>
> The update site URL, ID, and version I obtained from the GEF feature.xml
> file. What I'm doing is trying to utilize update manager functionality
for
> installing EMF and GEF during GMF's automated build process.
>
> When I execute this command, I get the following error:
>
> org.eclipse.core.runtime.CoreException[0]:
org.eclipse.core.runtime.CoreException[0]:
> java.io.IOException: Server returned HTTP response code: "404 Not Found"
> for URL:
http://update.eclipse.org/updates/plugins/org.eclipse.draw2d _3.1.0.jar.
>
> After some investigation, it seems the update manager resolves the
feature's
> plug-ins to a default location based on the update site root, followed by
> '/plugins/<plug-in name>.<version>.jar', if it does not find a reference
> to the plug-in location in the site.xml file. For GEF features, it seems
> the older site.xml references the 3.0 update locations using URLs prefixed
> with '3.0/' (and, this seems to be a GEF exclusive). So, the feature
itself
> is matched, but plug-in references are resolved as in the above, without
> '3.0/' in the path, and therefore causing the 404 Not Found error.
>
> If I use http://update.eclipse.org/updates/3.0 for the -from argument, it
> works as expected. Note that the update manager works fine through the
GUI,
> as I suspect it is using the ../3.0/site.xml file (or is able to resolve
> the correct plug-in URLs by some other means).
>
> So, not sure if I'm missing something here, or if it's an issue with the
> update manager... but it seems if the URL in the feature.xml were to point
> to http://update.eclipse.org/updates/3.0 all would be well.
>
> Thanks,
> Rich
>
>
|
|
|
| Re: Problem with command line update manager [message #190585 is a reply to message #190561] |
Thu, 04 August 2005 17:51 |
Richard Gronback
Messages: 605
Registered: July 2009 |
Senior Member |
|
|
Great, thanks!
> The update URL will be fixed in 3.1.1.
>
> <richard.gronback@borland.com> wrote in message
> news:1e24834217ff68c766eb2d217b40@news.eclipse.org...
>> I've tried to download GEF 3.1.0 using the following options via the
>>
> command
>
>> line (standalone) update manager:
>>
>> -command install -featureId org.eclipse.gef -version 3.1.0 -from
>>
> http://update.eclipse.org/updates/
>
>> The update site URL, ID, and version I obtained from the GEF
>> feature.xml file. What I'm doing is trying to utilize update manager
>> functionality
>>
> for
>
>> installing EMF and GEF during GMF's automated build process.
>>
>> When I execute this command, I get the following error:
>>
>> org.eclipse.core.runtime.CoreException[0]:
>>
> org.eclipse.core.runtime.CoreException[0]:
>
>> java.io.IOException: Server returned HTTP response code: "404 Not
>> Found" for URL:
>>
> http://update.eclipse.org/updates/plugins/org.eclipse.draw2d _3.1.0.jar
> .
>
>> After some investigation, it seems the update manager resolves the
>>
> feature's
>
>> plug-ins to a default location based on the update site root,
>> followed by '/plugins/<plug-in name>.<version>.jar', if it does not
>> find a reference to the plug-in location in the site.xml file. For
>> GEF features, it seems the older site.xml references the 3.0 update
>> locations using URLs prefixed with '3.0/' (and, this seems to be a
>> GEF exclusive). So, the feature
>>
> itself
>
>> is matched, but plug-in references are resolved as in the above,
>> without '3.0/' in the path, and therefore causing the 404 Not Found
>> error.
>>
>> If I use http://update.eclipse.org/updates/3.0 for the -from
>> argument, it works as expected. Note that the update manager works
>> fine through the
>>
> GUI,
>
>> as I suspect it is using the ../3.0/site.xml file (or is able to
>> resolve the correct plug-in URLs by some other means).
>>
>> So, not sure if I'm missing something here, or if it's an issue with
>> the update manager... but it seems if the URL in the feature.xml were
>> to point to http://update.eclipse.org/updates/3.0 all would be well.
>>
>> Thanks,
>> Rich
|
|
|
Goto Forum:
Current Time: Thu Dec 12 16:34:46 GMT 2024
Powered by FUDForum. Page generated in 0.03601 seconds |
] 
Search
Help
Register
Login
Home
