I have my own product catalog hosted, how do I update a product to Neon from Mars? [message #1740550] |
Mon, 15 August 2016 11:49  |
Eclipse User |
|
|
|
Basically I have my own product catalog hosted. It had only one product which was Mars JEE. It had a bunch of custom setup changes and steps.
Once Neon came out. I added a new product for Neon by copying it from the standard eclipse hosted product catalog, and then copied over all of my setup tasks. This worked great and as expected. Now my product catalog has two products, one for Neon and one for Mars. I have about 30 developers which installed eclipse with my custom installer back when it was just Mars. Now that I've added Neon, in order to update to Neon they have to re-run the installer and choose Neon, or change the installation product version property and restart eclipse.
Is there any way that I can just update the Mars product i have hosted to point at Neon so they will automatically get the update without any action on their part? Basically the same way that the official eclipse "Latest.." product works. How do I make the change to the Mars product catalog such that I can rename it, and change the p2 director to point to Neon so that my 30 developers will get the update automatically?
Basically what confuses me is this: How does eclipse determine which product it is? Is there some UID in the product definition in the catalog that it uses to determine which product it is even after change the name and p2 director to point to the latest version?
Thanks!
|
|
|
Re: I have my own product catalog hosted, how do I update a product to Neon from Mars? [message #1742046 is a reply to message #1740550] |
Mon, 15 August 2016 12:24   |
Eclipse User |
|
|
|
Taylor,
Comments below.
On 15.08.2016 17:49, Taylor Abrahamson wrote:
> Basically I have my own product catalog hosted. It had only one
> product which was Mars JEE. It had a bunch of custom setup changes and
> steps.
> Once Neon came out. I added a new product for Neon by copying it from
> the standard eclipse hosted product catalog, and then copied over all
> of my setup tasks. This worked great and as expected. Now my product
> catalog has two products, one for Neon and one for Mars. I have about
> 30 developers which installed eclipse with my custom installer back
> when it was just Mars. Now that I've added Neon, in order to update to
> Neon they have to re-run the installer and choose Neon, or change the
> installation product version property and restart eclipse.
>
> Is there any way that I can just update the Mars product i have hosted
> to point at Neon so they will automatically get the update without
> any action on their part?
No.
> Basically the same way that the official eclipse "Latest.." product
> works.
That works because we change the definition in place at that named
product version.
> How do I make the change to the Mars product catalog such that I can
> rename it, and change the p2 director to point to Neon so that my 30
> developers will get the update automatically?
The reference to the product version is stored in the
installation.setup. E.g., like this:
<productVersion
href="index:/org.eclipse.setup#//@productCatalogs[name='org.eclipse.products']/@products[name='epp.package.committers']/@versions[name='mars']"/>
You can't rename anything in the catalog because the product version is
located by name. If you wanted a "moving target" you should have copied
the style we used and has a version named "latest.released" to which you
copied product version you added when you added neon.
>
> Basically what confuses me is this: How does eclipse determine which
> product it is?
Eclipse or Oomph? Oomph stores this in the installation.setup, which
you can open with Navigate -> Open Setup -> Installation.
> Is there some UID in the product definition in the catalog that it
> uses to determine which product it is even after change the name and
> p2 director to point to the latest version?
The product catalogs we generate generate a copy of the neon product
version to the latest.released product version so the switch happens
automatically when we update what's represented in the catalog.
I'm not sure if your goal is that developers can install mars or neon
versions, or if you want just a single product version that you update
when there is a new release. At this point you've taken the former
approach...
>
> Thanks!
|
|
|
|
Powered by
FUDForum. Page generated in 0.58200 seconds