|Re: referencing VIATRA feature s in our own feature [message #1748371 is a reply to message #1748358]
||Tue, 22 November 2016 14:42
| Zoltan Ujhelyi
Registered: July 2015
I am not exactly sure what do you want to achieve, but I try to explain all options I see for this reason. If I did not meet your use case, please clarify.
* If you want to add the Obfuscator to the Papyrus Additional Component Discovery, you can add our features from directly in our update site by referring it in the XML file. By looking at the source code of Papyrus, it loads the description from http://www.eclipse.org/modeling/mdt/papyrus/downloads/discovery/neon/papyrus-extra.xmi; however, I don't know whether how that file is managed.
* If you want to add the model obfuscator to the Papyrus update site as an extra feature, the easiest way to achieve it to add our feature to your target definition, and then add it to your category.xml file.
* If you want to add the model obfuscator as a dependency of a Papyrus-specific feature, you have to add our feature to your target definition, and add the obfuscator as a dependency to your feature in the feature.xml editor.
Regardless of the path you choose, I would like to mention here that so far the Obfuscator was not added to the releases of VIATRA and is still considered as an incubation feature of VIATRA. We decide to miss releases, because the tool has seen limited testing on our side, and we are not sure whether it is release-ready as of now. However, if the tool seems stable enough, we can do some releases.
Powered by FUDForum
. Page generated in 0.01945 seconds