Home » Eclipse Projects » Oomph » Automatic Plugin Updates(Update eclipse plugins automatically)
| Automatic Plugin Updates [message #1716473] |
Fri, 04 December 2015 09:07  |
|
Hey guys
Is there really no mechanism to automatically update plugins with Oomph?
The update mechanism of eclipse isn't usable, because it leads to conflicts with oomph's version ranges. (eclipse update mechanism doesn't respect oomph's version ranges)
To expect that all our users have to click "Perform Setup Tasks..." manually to update a plugin, is no solution. Is a feature planned to automatically update plugins?
Or at least give the user a message that new versions of plugins are available.??
This problem makes it difficult for us to use Oomph at all.
|
|
|
| Re: Automatic Plugin Updates [message #1716546 is a reply to message #1716473] |
Fri, 04 December 2015 17:12  |
|
Hi Stefan,
Comments below...
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 04.12.2015 um 14:56 schrieb Stefan Kapferer:
> Hey guys
>
> Is there really no mechanism to automatically update plugins with Oomph?
You mean to automatically perform setup tasks (including p2 director tasks) in specific intervals?
>
> The update mechanism of eclipse isn't usable, because it leads to conflicts with oomph's version ranges. (eclipse
> update mechanism doesn't respect oomph's version ranges)
I also don't really understand why p2 requires you to specify IUs (i.e., exact versions) on the top level, in contrast
to requirements (i.e., version ranges) on all other levels of the dependency graph.
>
> To expect that all our users have to click "Perform Setup Tasks..." manually to update a plugin, is no solution. Is a
> feature planned to automatically update plugins?
It has been discussed but we currently have no concrete plans to work on that.
> Or at least give the user a message that new versions of plugins are available.??
From Oomph's perspective the P2 Director task is just one of the relevant tasks, so I don't expect that we add special
functionality or UI for just that one type of task.
>
> This problem makes it difficult for us to use Oomph at all.
You mean because Oomph has no automatic perform trigger you can't use it? That's hard to believe, but maybe I still
don't understand your problem.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
| |
| Re: Automatic Plugin Updates [message #1716586 is a reply to message #1716546] |
Sat, 05 December 2015 15:09 |
|
Hi Eike,
Thanks for the answer. Comments bellow...
Cheers, Stefan
Am 04.12.2015 um 14:56 schrieb Stefan Kapferer:
> Hey guys
>
> Is there really no mechanism to automatically update plugins with Oomph?
> You mean to automatically perform setup tasks (including p2 director tasks) in specific > intervals?
Yes. If I publish new versions of our eclipse plugins into our P2-Repository, they have to be updated in all eclipse's without manual interaction.
>
> The update mechanism of eclipse isn't usable, because it leads to conflicts with oomph's version ranges. (eclipse
> update mechanism doesn't respect oomph's version ranges)
> I also don't really understand why p2 requires you to specify IUs (i.e., exact versions) on > the top level, in contrast
> to requirements (i.e., version ranges) on all other levels of the dependency graph.
In fact we don't need Oomph's version ranges. The default eclipse update mechanism would be completely ok for us. But I have read somewhere (Oomph documentation or FAQ's) that you should not use eclipse's update mechanism.
>
> To expect that all our users have to click "Perform Setup Tasks..." manually to update a plugin, is no solution. Is a
> feature planned to automatically update plugins?
> It has been discussed but we currently have no concrete plans to work on that.
Ok. Thanks for that answer.
> Or at least give the user a message that new versions of plugins are available.??
> From Oomph's perspective the P2 Director task is just one of the relevant tasks, so I
> don't expect that we add special
> functionality or UI for just that one type of task.
Okay.
>
> This problem makes it difficult for us to use Oomph at all.
> You mean because Oomph has no automatic perform trigger you can't use it? That's
> hard to believe, but maybe I still
> don't understand your problem.
As I already mentioned I just need a mechanism which automatically updates our eclipse plugins. We work on a big project/product and have a lot of developers. We implement eclipse plugins for them and when we publish updates of these plugins we want to be shure that they get them as soon as possible. The classic eclipse update mechanism was perfect, because after each restart of eclipse, the user got a message that there are updates. With Oomph I did't find a similar solution until now. Maybe I miss something. At the moment our Oomph solution doesn't check for updates at all after the setup is done once.
|
|
|
| Re: Automatic Plugin Updates [message #1716587 is a reply to message #1716583] |
Sat, 05 December 2015 15:19 |
|
Hi Alex
> Where does the project setup for your users come from? If it is not a local copy for
> everybody, why do you not simply raise the required versions of the plugins in the setup? > In that case, users do not have to perform the setup task manually - updates will be
> performed by Oomph on startup. (We host the project setup file on a file server
> accessible to all users and have no problems with the above approach.)
We have the setup-Files in a Git-Repository, which is cloned for every user. So the user has a local copy of them...
I don't want to change these version ranges, in fact we don't need it.
But... For example we defined a version range of [1.0.0 - 2.0.0]. I expect that, if I
publish a new Version of our Plugin with version 1.5.3 in our P2 repository, that Oomph updates the plugin. (Oomph initially installed 1.5.2) Without changing anything on the setup...
Maybe I do something wrong, but Oomph does not check for plugin updates at startup at the moment. After the user has setup he's eclipse, Oomph never checks for new versions of the plugins in our P2-Repository again.
|
|
| |
| Re: Automatic Plugin Updates [message #1716608 is a reply to message #1716603] |
Sun, 06 December 2015 09:27 |
|
Hi Alex
> Hi Stefan,
> defining the version range [1.0.0-2.0.0] states that version 1.5.2 is OK, so an update to 1.5.3
> is not *required*. There is no need for Oomph to recheck for updates as the current
> eclipse meets the definitions in the setup file. This is how Oomph currently works. You
> can achieve the desired behaviour by changing the minimum version. In this case,
> Ooomph would initialize the update. It is not such a great effort for one person to change
> the setup in order for all others to have a up to date eclipse. Of course, your approach of
> shipping the setup file via local git clones is far from optimal for that, as now each user
> has to pull the changes first... Think about a central setup immediately visible to all users.
Thank you very much for that hint. I didn't expected that Oomph's version ranges work that way. So, you are right. In that case, changing the minimum version would do the trick.
Our approach with the Git repository isn't that bad. Our users work with our own command line tool, which is a facade for all our dev-tools. They don't start oomph or eclipse by themselves. Everything is behind our command line and it does the pull to update the product setups automatically 
Our users don't have to do any manual steps. They just enter one command for starting eclipse on the command line, the rest is done automatically...
And our setups are versioned, which is a nice side effect of that solution.
> Alex
> P.S.: Are you aware of the possibilities for distributing custom product and project
> catalogs without the need for each user to add setups to the user catalogs?
What do you mean exactly? You mean we don't need the setup-files on the local filesystem when executing the installer?
Thank you very much for your answer!
|
|
|
| Re: Automatic Plugin Updates [message #1716610 is a reply to message #1716608] |
Sun, 06 December 2015 10:41 |
 Alexander Nittka
Messages: 1193
Registered: July 2009 |
Senior Member |
|
|
Hi Stefan,
as local setup updates are automated, everything is be fine as it is (I withdraw the criticism - given the described process).
Regarding the catalog distribution I mentioned: The installer uses an "index" containing product and project catalogs you can choose the desired setups from. In order to make your own project setups installable, there are several ways (and obviously you have found one for your use case). You can file a ticket for your setup to be included in an official catalog, you can ask your users to add the setup to the user projects (manual user steps needed) or you can redirect the entire index (or catalogs), so that your setups are visible automatically (less manual user steps needed). The last approach is briefly explained e.g. in the Oomph Authoring wiki https://wiki.eclipse.org/Eclipse_Oomph_Authoring#Hosting_your_own_index_.2F_catalogs
One note of warning regarding updating plugins via setup changes: Oomph will not de-install any plugins and has no task for doing so. This implies that you cannot, e.g. replace one plugin in your setup with another while the two have conflicting dependencies (fresh installation works, but updating a running installation fails).
Alex
Need training, onsite consulting or any other kind of help for Xtext?
Go visit http://xtext.itemis.com or send a mail to xtext@itemis.de
[Updated on: Sun, 06 December 2015 10:57] Report message to a moderator |
|
| |
| Re: Automatic Plugin Updates [message #1716616 is a reply to message #1716610] |
Sun, 06 December 2015 12:55 |
|
Am 06.12.2015 um 11:41 schrieb Alexander Nittka:
> One note of warning regarding updating plugins via setup changes: Oomph will not de-install any plugins and has no
> task for doing so. This implies that you cannot update a plugin which in turn introduces a dependency conflicting with
> the currently running eclipse - even if the setup in itself is consistent (fresh installation works, but updating a
> running installation fails).
I had the feeling that someting's wrong about this statement, but after studying the complex code for a while I'm no
longer sure. It might be true that changing the requirement from [1.0,1.2) to [1.2,1.3) creates a conflict with the
current profile when it probably shouldn't. Changing from [1.0,2.0) to [1.1,2.0] would probably work, though.
Can you please submit a bugzilla so that we investigate this more thoroughly?
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: Automatic Plugin Updates [message #1716777 is a reply to message #1716616] |
Tue, 08 December 2015 07:51 |
|
Hi Eike
I thought that we talk about version conflicts between different eclipse plugins.
But if I understand your statement, it's also possible that Oomph gets conflicts when
updating plugins independent if there are plugin version conflicts or not.?
Cheers
Stefan
|
|
| | |
Goto Forum:
Current Time: Sat Dec 07 02:31:14 GMT 2024
Powered by FUDForum. Page generated in 0.04954 seconds |
] 
Search
Help
Register
Login
Home
