| Combine Product and Project setup [message #1819184] |
Thu, 09 January 2020 16:13  |
|
Is it possible to have one setup file which defines the product and the project (which can be dragged onto the simple mode)?
Currently if someone wants to contribute to Dartboard he first needs to select a product and afterwards can add the project setup file via DnD. If he drag the file on the wrong location or page he gets an not so telling error.
I think it would be nice if a user could simply drop one file onto the simpler mode and gets a fully configured Eclipse with the project setup.
Is that possible? Didn't find documentation for that in https://wiki.eclipse.org/Eclipse_Oomph_Authoring
Best regards, Lars
Attachment: dnd.png
(Size: 81.14KB, Downloaded 282 times)
|
|
|
|
|
|
|
|
|
| Re: Combine Product and Project setup [message #1820975 is a reply to message #1819328] |
Mon, 03 February 2020 18:12  |
|
Thanks, Ed and Eike, worked fine.
FYI - In addition to copying the setup from the project setup file to the Workspace node I had also to setup scope.project.stream.name and scope.project.label. Stream seems to be missing in the context menu of Workspace node in the configuration model editor.
<setupTask
xsi:type="setup:VariableTask"
name="scope.project.stream.name"
value="master"
label="scope.project.stream.name"/>
<setupTask
xsi:type="setup:VariableTask"
name="scope.project.label"
value="master"
label="scope.project.label">
<description>Label</description>
</setupTask>
|
|
|
| Re: Combine Product and Project setup [message #1820984 is a reply to message #1820975] |
Tue, 04 February 2020 05:28 |
 Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
Why would you copy a project setup to the Workspace? The wiki doesn't suggest doing that:
https://wiki.eclipse.org/Eclipse_Oomph_Authoring#Automation_and_Specialization_with_Configurations
It mentions "The Configuration's Installation can reference a specific Product Version and the Configuration's Workspace can optionally reference several specific Project Streams." I.e., a Workspace reuses existing Project setups by virtue of the Workspace.streams cross reference. The wiki also mentions "Similarly, the Workspace's Project Streams are selected in the wizard and the wizard advances to the next page. " So do not copy setups because then of course you'll have to maintain two copies instead of one; simply reuse them.
Its always good to look at other examples, e.g., at this one for Oomph:
https://git.eclipse.org/c/oomph/org.eclipse.oomph.git/tree/setups/configurations/OomphConfiguration.setup
Those samples are available in every Setup editor. Even more convenient, if you use Navigate -> Open Setup -> Parent Models -> Catalog Index Eclipse, all the Configurations are shown in the Outline view.
Note that if you commit your Configuration to git.eclipse.org, it will be important to reference it from some other setup resource so that it's archived into the setups.zip. That can be accomplished with an annotation like this in your Project setup:<?xml version="1.0" encoding="UTF-8"?>
<base:Annotation
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:base="http://www.eclipse.org/oomph/base/1.0"
source="ConfigurationReference">
<reference
href="platform:/resource/setups/configurations/OomphConfiguration.setup#/"/>
</base:Annotation>
Just create an Annotation on the Project's context menu (New Child -> Annotation), drag and drop the Configuration's resource into the Project's Setup Editor, expand the resource node, and link drag (Alt-drag on Windows) the Configuration onto the Annotation to author this.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03879 seconds
] 
Search
Help
Register
Login
Home
