Archive command fails when model contains versioned imports.

[martinhalford]

Bug Report 🐛

The cicero archive command fails if the model.cto contains versioned imports or specifies a versioned namespace.

Current Behavior

• Take the current helloworld@0.14.0.cta archive and modify its package.json file to use cicero 0.24.0.

  "accordproject": {
      "template": "clause",
      "cicero": "^0.24.0",
      "runtime": "ergo"
  },

• Confirm the namespace at the top of the model.cto looks like this...

  namespace org.accordproject.helloworld

• Execute the command cicero archive and the following output is displayed

  % cicero archive
  10:53:07 am - INFO: Using current directory as template folder
  10:53:09 am - INFO: Creating archive: helloworld@0.14.0.cta

• Now modify the namespace at the top of the model.cto to look like this...

  namespace org.accordproject.helloworld@0.14.0

• Execute the command cicero archive and the following output is displayed

  % cicero archive
  10:53:41 am - INFO: Using current directory as template folder
  10:53:41 am - ERROR: Expected identifier but "0" found. File /Users/martin/helloworld/model/model.cto line 1 column 40

Expected Behavior

As we "cannot use an unversioned import org.accordproject.contract when 'strict' option on Model Manager is set" then the cicero archive command should accept versioned namespaces and imports.