|
|
| Re: switching target platform version [message #1706619 is a reply to message #1706615] |
Fri, 28 August 2015 07:55   |
|
On 28/08/2015 09:44, Eike Stepper wrote:
> Am 28.08.2015 um 09:21 schrieb Lorenzo Bettini:
>> Hi
>>
>> is there a way to perform setup tasks again to switch the target
>> platform version? For example, say that I chose "Luna" and now I want
>> to switch to "Mars" for the targlets; should I recreate the whole
>> workspace from scratch?
> No, you can do a normal manual perform and click "Show all variables".
> Then the TP variable should be shown and can be changed.
Hi
by "Manual perform" do you mean start the installer, not run perform
tasks from the workspace right? Because I don't see "show all
variables" when manually running perform tasks from the workspace.
thanks
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
|
|
|
|
|
| Re: switching target platform version [message #1782222 is a reply to message #1782221] |
Tue, 20 February 2018 15:38 |
|
The Master streams in all Platform subprojects (except SWT) contains a VariableTask, which defines the value of the eclipse.target.platform variable to be either Photon or Oxygen (approx. 50/50). That means this variable already has got a value and is, hence, not prompted at all. I assume that's on purpose, but only the Platform.setup maintainer can confirm. I further guess that this predefined value should be Photon for the Master streams of all subprojects, but again, only the Platform.setup maintainer can confirm.
In the meantime you could work around the problem by adding the following setup task to your user setup:
<?xml version="1.0" encoding="UTF-8"?>
<setup:VariableTask
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
name="eclipse.target.platform"
value="Photon"
storageURI="scope://Workspace">
<restriction
xsi:type="setup:Stream"
href="index:/org.eclipse.setup#//@projectCatalogs[name='org.eclipse']/@projects[name='platform']/@projects[name='runtime']/@streams[name='master']"/>
</setup:VariableTask>
You can copy this XML snippet directly to your Setup editor. Note that the variable override is restricted to the Master stream of the Platform Runtime project.
|
|
|
|
| Re: switching target platform version [message #1782228 is a reply to message #1782223] |
Tue, 20 February 2018 18:54 |
|
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 #1782243 is a reply to message #1782239] |
Tue, 20 February 2018 20:02 |
 Mario Jauvin
Messages: 34
Registered: October 2015 |
Member |
|
|
Maybe the pertinent questions are:
- How can I invoke oomph (eclipse installer) to create working workspaces for any of its projects targeted at Oxygen?
- Are there commands that can create successfully the appropriate Oxygen workspace that was used by the various Eclipse projects during their development and maintenance of Oxygen?
- Are there some conventions that must be adhered to by any projects in terms of tags, target platform specification/overriding?
I apologise if my questions appear weird. They do so because I do not know how things work internally. What I am looking for is a way to open any projects targeted at Oxygen regardless of what version is currently being developed. I am assuming this exists because it is necessary so as to permit the various project teams to support previous versions and because this is usually not difficult to do with some simple conventions.
As was noted in another Topic you said that some photon support was necessary in the platform UI setup (failing on a org.apache.batik.i18n requirement). Since the platform.ui setup was configured for Oxygen I assumed that the dependency on the Photon requirements introduced by something in oomph and not in the platform.ui setup. Again my apologies if my assumptions are incorrect.
[Updated on: Tue, 20 February 2018 20:12] Report message to a moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.02650 seconds
Search
Help
Register
Login
Home
