Uploaded image for project: 'Alloy'
  1. Alloy
  2. ALOY-1489

Support defining supported Alloy version range in config.json

    Details

    • Type: New Feature
    • Status: Open
    • Priority: None
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Tooling
    • Labels:
      None

      Description

      I'd like to be able to set a supported Alloy version range for an app in config.json:

      {
      	"global": {
      		"supportedAlloyVersions": ">=1.5.0 <1.8.0"
      	},
      	...
      }
      

      When Alloy compiles it should check if the Alloy version used to compile is supported by the Alloy app and if not fail with a clear message:

      [INFO]  Found Alloy app in /Users/fokkezb/dev/projects/ti-html2as/example/app
      [INFO]  Executing Alloy compile: /Users/fokkezb/.nvm/versions/node/v0.12.13/bin/node /usr/local/bin/alloy compile /Users/fokkezb/dev/projects/ti-html2as/example/app --config platform=ios,version=0,simtype=none,devicefamily=universal,deploytype=development,target=simulator
      [ERROR] Alloy app supports Alloy >=1.5.0 <1.8.0, not 1.8.2
      

      The primary use case for this are our release sample apps which often require the latest Alloy version to be used and might not always be updated for later Alloy versions (DE-359).

      But it would also make sense for open source apps and even in larger development teams it would be great to know why a project fails building instead of having to figure out what Alloy version an app was made for.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                batman Bruce Wayne
                Reporter:
                fokkezb Fokke Zandbergen
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Backbone Issue Sync

                  • Backbone Issue Sync is enabled for your project, but we do not have any synchronization info for this issue.

                    Git Integration