Titanium JIRA Archive
Alloy (ALOY)

[ALOY-85] Need to make ti.alloy compiler plugin work consistently

GitHub Issuen/a
TypeBug
PriorityHigh
StatusResolved
ResolutionFixed
Resolution Date2012-09-25T21:55:36.000+0000
Affected Version/sn/a
Fix Version/s2012 Sprint 20, Release 3.0.0
ComponentsTitanium SDK, Titanium Studio
Labelsn/a
ReporterTony Lukasavage
AssigneeUnknown
Created2012-07-16T07:33:38.000+0000
Updated2018-03-07T22:25:41.000+0000

Description

Current problems with ti.alloy plugin: * Will not work on Windows * nodejs path is hard-coded to /usr/local/bin/node * alloy path is hard-coded to /usr/local/bin/alloy These would be fairly easy to solve, but it appears as though compiler plugins launched through TiStudio do not have full access to the user's environment variables. My own $PATH is pretty large, but when inspected in the compiler plugin, it returns only 
/usr/bin:/bin:/usr/sbin:/sbin
 So we need a more reliable way to configure this plugin until we have true Titanium Studio integration. Either that or we continue to post workarounds as users encounter issues.

Comments

  1. Tony Lukasavage 2012-07-16

    Something to consider is the CLI rewrite and upcoming TiStudio integration that would eliminate much of these issues. How much effort do we want to put into improving something that may soon be obsolete?
  2. Russell McMahon 2012-07-16

    Probably this is a post pre-release issue. Unless it is super simple to fix. There are also issues of how if we fix up python scripts how are we going to distribute with alloy, if we have developers override exiting build scripts we could introduce build regression not tested by QA.
  3. Tony Lukasavage 2012-09-19

    Dependency has been resolved. Need to determine the minimum version this will be available in for TiStudio and code around that accordingly.

JSON Source