Titanium JIRA Archive
Alloy (ALOY)

[ALOY-1489] Support defining supported Alloy version range in config.json

GitHub Issuen/a
TypeNew Feature
PriorityNone
StatusOpen
ResolutionUnresolved
Affected Version/sn/a
Fix Version/sn/a
ComponentsTooling
Labelsn/a
ReporterFokke Zandbergen
AssigneeBruce Wayne
Created2016-04-08T08:39:14.000+0000
Updated2016-04-08T08:46:08.000+0000

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](https://github.com/appcelerator-developer-relations/?query=appc-sample-ti) 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.

Comments

No comments

JSON Source