Deterministic Product Build [message #1749896] |
Tue, 13 December 2016 15:24 |
|
Hello all,
I want to provide a deterministic product build. Currently, as I understand the oomph engine, I can specify a version to a plugin. But in the case of the plugin having unrestricted dependencies the engine would load the most recent of those dependencies.
I would like to provide a stable product that will be the same on each machine, no matter where or when I run the installer. Is there a way to extract a product from a given eclipse installation?
I also heart, that it should be possible to point to a zip file instead of a setup ecore model. How would I do that?
Thanks in advance
"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live" - John Woods
|
|
|
|
Re: Deterministic Product Build [message #1750949 is a reply to message #1749939] |
Mon, 02 January 2017 15:47 |
|
And what about the zip solution? I heard from a colleague who talked to you at eclipse con that it would be possible to use a zipped eclipse as some kind of setup file.
"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live" - John Woods
|
|
|
Re: Deterministic Product Build [message #1750970 is a reply to message #1750949] |
Tue, 03 January 2017 08:57 |
Ed Merks Messages: 33258 Registered: July 2009 |
Senior Member |
|
|
Well, Oomph itself will use a p2 task to create an installation. Of course installations are also distributed at Eclipse as zip files and tar files, so in theory you could create an installation that way, but without a p2 task, the installer will have no idea that an installation is being created. The latest version of the Repository Explorer (from a nightly build) includes the current installation profile as a repository choice. And the context menu supports multiple selection and Copy with Version Range (where the range is determined by control in the lower right of the view), so by setting that to Qualifier, it's easy to create a set of requirements that locks in highly specific versions.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.05079 seconds