Skip to content
This repository has been archived by the owner on Feb 29, 2020. It is now read-only.

Add an ACLI Provider #4

Open
Phillipus opened this issue Dec 11, 2019 · 9 comments
Open

Add an ACLI Provider #4

Phillipus opened this issue Dec 11, 2019 · 9 comments

Comments

@Phillipus
Copy link
Member

This is now implemented.

Open to suggestions to change the CL parameters which are:

--portico.import "mymodel.archimate" --portico.replace

BTW - there is also a Feature project which makes things easier when you run from Eclipse.

@jbsarrodie
Copy link
Member

--portico.replace

If this option is equivalent to the "update" GUI option, then why not simply call it --portico.update or --portico.allowUpdate?

BTW: I sometime wonder if portico is the right name to use. At least, for not native speaker it doesn't ring a bell.

@Phillipus
Copy link
Member Author

Sure, why not.

BTW: I sometime wonder if portico is the right name to use. At least, for not native speaker it doesn't ring a bell.

I think this should eventually be part of the Archi core and this plugin is the "punkworks" project until we get it all working. :-)

@Phillipus
Copy link
Member Author

I think this should eventually be part of the Archi core and this plugin is the "punkworks" project until we get it all working. :-)

And then name it something plain like com.archimatetool.com.importer

@jbsarrodie
Copy link
Member

I think this should eventually be part of the Archi core and this plugin is the "punkworks" project until we get it all working. :-)

And then name it something plain like com.archimatetool.com.importer

Agree :-)

@Phillipus
Copy link
Member Author

Agree :-)

I'll rename the ACLI arguments accordingly.

We should continue and beta test in this separate plug-in and then when we think it's bug free we can put it in Archi core code.

@Phillipus
Copy link
Member Author

Phillipus commented Dec 14, 2019

Current CLI options are:

--importModel "mymodel.archimate" --importModel.update --importModel.updateAll

--updateAll implies --update

@Phillipus
Copy link
Member Author

Phillipus commented Dec 14, 2019

I wonder if we could improve that to something like:

--importModel.update "all" | "none" | "objects"

@jbsarrodie
Copy link
Member

I suppose that --importModel.update set "update" mode on and --importModel.updateAll does the same but also update model and top level folders ?

I wonder if we could improve that to something like:
--importModel.update "all" | "none" | "objects"

I have two issues with this:

  1. It is longer than simply --importModel.update or --importModel.updateAll
  2. I don't find objects very intuitive but I can't find a better wording

So I would stick with your first suggestion

@Phillipus
Copy link
Member Author

I suppose that --importModel.update set "update" mode on and --importModel.updateAll does the same but also update model and top level folders ?

Yes, that's it

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants