| Re: [papyrus-rt-dev] Update the Model Import tool for Neon |
|
Hi, I’ve pushed a new patch set to include the RSA-RTE importer in a separate feature. However, this raises some additional
questions: -
Currently, we have 3 builds and 3 features:
o
Profile
o
Core
o
Tooling It seems that the RSA Importer makes sense in the Tooling build, but not in the tooling feature. Thus, the new patch set
adds a new feature (RSA Importer) included in the Tooling build. Should we configure a separate build for this? -
I’ve added the RSA Importer feature to the top-level Papyrus-RT Feature. Does that make sense as well? If the
end-user doesn’t want to install the RSA Importer, then he needs to manually check Profile + Core + Tooling, without the RSA Importer. But the top-level feature is supposed to contain everything else, so... not sure what’s best Regards, De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de LETAVERNIER Camille Hi Peter, Ø
maybe we should put this into its own feature, instead of including it directly in the tooling feature I have no opinion on this, so, whatever the Papyrus-RT team prefers :) I’ll add a separate feature Ø
When the RSARTE specific import extension is installed, do you also have to install the RSA import feature from Papyrus?
Or will the RSA import functionality included automatically? The standard RSA Import from Papyrus is automatically installed when installing the Papyrus-RT Import (provided that the
Papyrus Extra update site is available, so this depends on your deployment). The extension adds no extra UI, it works exactly in the same way (Except that it adds support for Papyrus-RT rather than discarding the profile and stereotypes). Additional UI might
be required if e.g. the RSA-RTE Import needs specific import options. But so far, this didn’t seem to be a use case Regards, De :
papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Peter Cigéhn Hi Camille, As I commented on the Gerrit change, maybe we should put this into its own feature, instead of including it directly in the tooling feature? Since the import tool is a rather "one-shot"-kind
of functionality, I guess it would be good if it could be installed optionally for those that don't want/need it. The new import feature could still be included in the top level Papyrus-RT feature in the same way as profle, core and tooling is already. For my understanding also: When the RSARTE specific import extension is installed, do you also have to install the RSA import feature from Papyrus? Or will the RSA import functionality included
automatically? In practice, how will it work from an end-user perspective? Will it be the different sets of import options in the import wizard, or do the RSARTE specific import just extends the existing RSA
import function, in practice causing it to to be able to also import RSARTE models? /Peter Cigéhn On 7 April 2016 at 13:06, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote:
|