|Conditional project catalog? [message #1778055]
||Fri, 08 December 2017 16:50
| Vincent Zurczak
Registered: July 2009
I have another question, about project catalogs this time.
Maybe I should explain our use case first. We maintain our own Eclipse distributions: they are based on official ones but come with additions and a custom configuration. All of this is achieved through a preconfigured OOMPH installer. It also implies we have our own catalog.
Now, we have different product versions, based on different versions of Eclipse.
And we would like to have different projects based on the selected version. One version will be the new one and will have an updated project catalog (maybe with new features). While the catalogs for old product versions would only be kept for maintenance.
Maybe this structure will help to understand:
The question is about whether it is possible to show the projects of oxygen.projects.setup when the user selects the oxygen version or neon.projects.setup when the user selects the neon version. For the moment, we only have a common set of projects, but we cannot assume new additions will be compatible with old versions.
As an example, we have a setup task that downloads a version of Tomcat.
If we add a new version of Tomcat, we cannot be sure it will work with older versions of Eclipse. So, with this example, we would like to freeze old versions (both products and projects) and add a new one.
How can we define a conditional selection of a project catalog?
I have seen filters, but they apply to setup tasks only. We would need this but at a higher level (based as an example on the scope.product.version.name variable). Is this possible?
Powered by FUDForum
. Page generated in 0.02178 seconds