-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to be able change version of Alloy that is used with Appc CLI #4
Comments
@brentonhouse if you'd like to contain this within the adamantium project you could install a global CLI hook as part of installing the global Alloy CLI. See how TiShadow does the same: https://github.com/dbankier/TiShadow/blob/master/package.json#L47 |
@FokkeZB Maybe even create a parameter that could enable/disable it so that you could compile using "real" alloy if you wanted to. |
That's probably not going to happen anymore as Alloy is being refactored. |
Couldn't I look for a parameter in |
All of CLI tooling is getting refactored, but of course until then you can introduce a option (like TiShadow does |
ah, gotcha. I will try to keep up w/ the changes to adapt. |
With the old build system (Titanium or Ti), I could simply run
npm install -g alloy@versionx
to get a different or custom build of Alloy used with a build. Now with the new build system (Appcelerator or Appc), A specific version of Alloy is bundled with the Appcelerator Platform and there is not a simple way to change it on all our developer and build machines.If there is known way of doing this already, please let us know!
We have an Enterprise license and this is critical for us right now as we have a memory leak that we need to patch in Alloy and get it into production quickly.
Associated JIRA Ticket: https://jira.appcelerator.org/browse/AC-661
Workaround
@FokkeZB proposed adding a global hook that contains this:
https://jira.appcelerator.org/browse/TIMOB-20512
The text was updated successfully, but these errors were encountered: