Home » Eclipse Projects » Eclipse Platform » Triggering updates?
| Triggering updates? [message #328934] |
Fri, 06 June 2008 16:45  |
Eclipse User |
|
|
|
I have a plugin, feature, and update site projects. I push "Build All"
on the update site and it creates a new .jar file with a new name. I
copy all of th new files to my update site. Then on my test eclipse I
push software update, "Update". I get "nothing to update". Hints?
Do I have to manually change the version numbers?
Thanks,
John.
|
|
| | |
| Re: Triggering updates? [message #328939 is a reply to message #328934] |
Fri, 06 June 2008 20:57  |
| Eclipse User |
|
|
|
John J Barton wrote:
> I have a plugin, feature, and update site projects. I push "Build All"
> on the update site and it creates a new .jar file with a new name. I
> copy all of th new files to my update site. Then on my test eclipse I
> push software update, "Update". I get "nothing to update". Hints?
>
> Do I have to manually change the version numbers?
I tried some combinations.
If I change the feature version number from 1.0.0 to 1.0.1, then the
client will update. But the PDE UI for this makes me think I can't be
doing the right things:
feature.xml, manually change 1.0.0 to 1.0.1
update.xml, select feature 1.0.0, remove it, add, add 1.0.1.
This worked eventually but surely this isn't the right way.
I also tried just changing the plugin's plugin.xml version number from
1.0.0 to 1.0.1. The client says no updates.
At this point I'd like to ditch all of the feature/update site stuff
since it does not work and doesn't seem to be documented. But how can I
update my users?
Is there any alternative to the eclipse update stuff?
John.
|
|
|
| Re: Triggering updates? [message #328963 is a reply to message #328939] |
Mon, 09 June 2008 09:07 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
John J Barton wrote:
> John J Barton wrote:
>> I have a plugin, feature, and update site projects. I push "Build All"
>> on the update site and it creates a new .jar file with a new name. I
>> copy all of th new files to my update site. Then on my test eclipse I
>> push software update, "Update". I get "nothing to update". Hints?
>>
>> Do I have to manually change the version numbers?
>
> I tried some combinations.
>
> If I change the feature version number from 1.0.0 to 1.0.1, then the
> client will update. But the PDE UI for this makes me think I can't be
> doing the right things:
> feature.xml, manually change 1.0.0 to 1.0.1
> update.xml, select feature 1.0.0, remove it, add, add 1.0.1.
> This worked eventually but surely this isn't the right way.
>
> I also tried just changing the plugin's plugin.xml version number from
> 1.0.0 to 1.0.1. The client says no updates.
>
> At this point I'd like to ditch all of the feature/update site stuff
> since it does not work and doesn't seem to be documented. But how can I
> update my users?
>
> Is there any alternative to the eclipse update stuff?
First of all, what version of Eclipse are you running? If it is 3.3, I'd
suggest you take a look at what 3.4 is doing with the p2 effort:
http://wiki.eclipse.org/Equinox_p2_Getting_Started
Second, to say that update stuff "does not work" is just argumentative.
Obviously you don't understand all of it and it has issues, but it does
work as thousands of people use it with success every day, on hundreds
of features.
I think the part you are missing is that update manager is based on
features, not plugins. That is why only changing the version of your
plugin had no affect. The process you described is the one I think has
to be followed:
>> feature.xml, manually change 1.0.0 to 1.0.1
>> update.xml, select feature 1.0.0, remove it, add, add 1.0.1.
>> This worked eventually but surely this isn't the right way.
Why do you label that as "surely not the right way?" The Feature is one
artifact, the Update Site is another. The two are, rightfully,
maintained independently. Honestly, I hope it is not just that you are
complaining about having to change two things in order to properly
configure a "latest current" update site. I hope there is more to your
question and complaint than that, because that is hardly what I would
consider a problem. Think about it, how else would you be able to
maintain an update site or multiple update sites that include different
versions of the same feature? That is exactly the kind of flexibility
that is built into the update mechanism, by intention. It is not just as
simple as "always use the latest version of every feature" - that would
not be flexible enough to serve the needs of the plugin dev community in
general.
Hope this helps,
Eric
|
|
|
| Re: Triggering updates? [message #328975 is a reply to message #328963] |
Mon, 09 June 2008 13:47 |
| Eclipse User |
|
|
|
Eric Rizzo wrote:
> John J Barton wrote:
>> John J Barton wrote:
>>> I have a plugin, feature, and update site projects. I push "Build
>>> All" on the update site and it creates a new .jar file with a new
>>> name. I copy all of th new files to my update site. Then on my test
>>> eclipse I push software update, "Update". I get "nothing to
>>> update". Hints?
>>>
>>> Do I have to manually change the version numbers?
>>
>> I tried some combinations.
>>
>> If I change the feature version number from 1.0.0 to 1.0.1, then the
>> client will update. But the PDE UI for this makes me think I can't be
>> doing the right things:
>> feature.xml, manually change 1.0.0 to 1.0.1
>> update.xml, select feature 1.0.0, remove it, add, add 1.0.1.
>> This worked eventually but surely this isn't the right way.
>>
>> I also tried just changing the plugin's plugin.xml version number from
>> 1.0.0 to 1.0.1. The client says no updates.
>>
>> At this point I'd like to ditch all of the feature/update site stuff
>> since it does not work and doesn't seem to be documented. But how can
>> I update my users?
>>
>> Is there any alternative to the eclipse update stuff?
>
> First of all, what version of Eclipse are you running? If it is 3.3, I'd
> suggest you take a look at what 3.4 is doing with the p2 effort:
> http://wiki.eclipse.org/Equinox_p2_Getting_Started
I'm running 3.4, my users who update may be on 3.3.
>
> Second, to say that update stuff "does not work" is just argumentative.
Ok, I'm sorry I let my frustration out. I would be grateful for any
help in figuring out how to get the wonderful eclipse update mechanism
to work. I have a plugin, feature, and update site. Can you tell me
what to do to cause my users to see updates? I could not find this in
the documentation.
(I did look at the P2 link, but it does not have this information).
Thanks,
John.
|
|
|
| Re: Triggering updates? [message #328986 is a reply to message #328963] |
Mon, 09 June 2008 17:18 |
| Eclipse User |
|
|
|
Eric Rizzo wrote:
> John J Barton wrote:
>> John J Barton wrote:
>>> I have a plugin, feature, and update site projects. I push "Build
>>> All" on the update site and it creates a new .jar file with a new
>>> name. I copy all of th new files to my update site. Then on my test
>>> eclipse I push software update, "Update". I get "nothing to
>>> update". Hints?
>>>
>>> Do I have to manually change the version numbers?
>>
>> I tried some combinations.
>>
>> If I change the feature version number from 1.0.0 to 1.0.1, then the
>> client will update. But the PDE UI for this makes me think I can't be
>> doing the right things:
>> feature.xml, manually change 1.0.0 to 1.0.1
>> update.xml, select feature 1.0.0, remove it, add, add 1.0.1.
>> This worked eventually but surely this isn't the right way.
>>
>> I also tried just changing the plugin's plugin.xml version number from
>> 1.0.0 to 1.0.1. The client says no updates.
>>
>> At this point I'd like to ditch all of the feature/update site stuff
>> since it does not work and doesn't seem to be documented. But how can
>> I update my users?
>>
>> Is there any alternative to the eclipse update stuff?
>
> First of all, what version of Eclipse are you running? If it is 3.3, I'd
> suggest you take a look at what 3.4 is doing with the p2 effort:
> http://wiki.eclipse.org/Equinox_p2_Getting_Started
>
> Second, to say that update stuff "does not work" is just argumentative.
> Obviously you don't understand all of it and it has issues, but it does
> work as thousands of people use it with success every day, on hundreds
> of features.
I re-read the documentation and tried the procedure as bast I could
figure it out:
Change the plugin version number 1.0.1 -> 1.0.2
Change the feature number 1.0.1 -> 1.0.2
On update site add new feature 1.0.2
Build all.
Go to the another machine with eclipse, Help->Software updates, update.
Popup says "There is nothing to update" So now I say for
Version: 3.4.0
Build id: I20080523-0100
It does not work. I'm not being argumentative: I think it is broken.
Is there a way to diagnose the update, some tracing or logging option.
Am I even doing the right steps?
Joh.
|
|
| | | |
| Re: Triggering updates? [message #329024 is a reply to message #329021] |
Tue, 10 June 2008 12:58 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
John J Barton wrote:
> Eric Rizzo wrote:
>> Hopefully someone else with more experience will step in to help. I'm
>> copying the PDE newsgroup in hopes that the audience there can do that...
>
> Hmmm I don't know about that group, eclipse.platform.pde does not come
> up on my list from news.eclipse.org.
I see from the message headers that you are using Thunderbird. In the
"Subscribe" dialog, make sure you hit the Refresh button to make sure it
has grabbed the latest list of groups from the server - e.p.pde is
relatively new.
Hope this helps,
Eric
|
|
|
Goto Forum:
Current Time: Sat May 03 13:38:29 EDT 2025
Powered by FUDForum. Page generated in 0.03714 seconds |
Home