|
|
|
|
|
|
|
Re: switching target platform version [message #1782228 is a reply to message #1782223] |
Tue, 20 February 2018 13:54   |
Eclipse User |
|
|
|
It would clearly be better if the Platform.setup maintainer providedseparate Oomph streams for their Git branches, not just Master. Then you could just select the Oxygen stream and start working.
Not all setup tasks support overriding, just the ones that implement the SetupTask.getOverrideToken() in a meaningful way. VariableTask and GitCloneTask are among those. The override snippet that I provided just overrides the value of the "eclipse.target.platform" variable, and that usually just impacts TargletTasks, not GitCloneTasks. But you can try to copy their GitCloneTask to your user.setup and then adjust it to your needs. I imagine there might be other tasks in their setup that would need adjustment, e.g., their API Baseline configuration (which is apparently controlled through the "eclipse.api.baseline.target.platform" variable).
Regarding your last sentence, I don't get that at all. It ends with a question mark, but I see no question. How is Oomph's own Git repo, or the lack of tags therein, related to the Platform setup?
|
|
|
|
|
Re: switching target platform version [message #1782261 is a reply to message #1782243] |
Tue, 20 February 2018 23:43  |
Eclipse User |
|
|
|
The projects themselves must support a setup description for older versions of their code. And there are of course two issues involved. Which versions of which tools are actually installed in the IDE and which versions of which features and bundles are in the target platform. Most tools can work with older versions in the target platform so it's not necessary to develop against Oxygen with an Oxygen IDE. To support such a thing a project generally creates a maintenance branch in their Git clone, and defines a Stream in the Project Setup with a name that corresponds to that named branch in their clone. In that stream they would define the variables necessary, for example, to select Oxygen as the eclipse.target. platform, and the would need to ensure that all their targlet tasks properly support a named repository list for resolving their requirements against Oxygen repositories containing Oxygen versions of those requirements.
The problem with the platform's setups is that their code in the master branch must have Photon repos listed to resolve all their requirements, but they've left their setup description so that it only tries to resolve Oxygen which is no longer correct/sufficient for how the master branch has evolved. If they maintained this properly they'd have a Stream corresponding to their Oxygen maintenance stream, and that would use the Oxygen eclipse.target.platform value, while the master branch would use Photon and they'd have named Repository lists that properly referred to Photon repositories. Nothing need be done in Oomph itself to fix this and nothing can be done in Oomph to address this. It must be the Project setup authors who do this; they have the commit rights to their own setups and I do not.
|
|
|
Powered by
FUDForum. Page generated in 0.10653 seconds