Project: appceleratorstudio
Issue TISTUD-3036: Index external build path entries separately from project index
Our current mechanism for build path entries is not as flexible and useful as we'll need to properly make use of it for NodeJs/Titanium/etc. Currently we can only have a contributor that supplies entries pointing at single files (JSCA), and hook them up to projects. The list is stored as a persistent property ont he project - which is not portable across workspaces and other users, so we should likely write them out to a {{.buildpath}} file likes JDT does with {{.classpath}}. Additionally, those files are "contributed" to the list run through our builder for a project. So they get merged into the project's index itself. For each build entry we should be able to point at a single file or a directory tree, and then index all of it. Each entry should be recorded into it's own index file, so multiple projects referencing the same entry can reuse the same index (i.e. Titanium SDK 2.1.4GA API). Lastly, the querying of indices would need to be altered os that we can ask for the ordered list of entries for a project, get the corresponding indices and query them. (rather than hard-coding the project's index and sometimes the "metadata" index).
Story points: 20