|Re: Combine Product and Project setup [message #1820984 is a reply to message #1820975]
||Tue, 04 February 2020 05:28
| Ed Merks
Registered: July 2009
Why would you copy a project setup to the Workspace? The wiki doesn't suggest doing that:|
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:
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"?>
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.
Powered by FUDForum
. Page generated in 0.04773 seconds