Move static resources outside src root

[Jonathan Toland]

Restated from #131. I regularly update src/ from Salesforce using MM. At that point I'm able to compare against git with my tool of choice. Because IC's backing directory is in src/staticresources/ it also gets blown away. I can accept my workflow is suboptimal. But my project should work regardless of editor (e.g. Force.com IDE) especially from a collaborative perspective (version control within ISVs). May I recommend either moving the backing directory to resource-bundles/{bundle-name}.resource/ (like MM) or at least make it configurable.

[Scott Wells]

Superficially this may seem quite simple, but it's actually quite a bit more complicated. It's very important that source files be under a registered source root or things won't work properly against those files. It doesn't have to be the same source root as the one used for the main metadata, though. I do agree that I don't want IC to collide with other IDEs as developers should be able to use tools-of-choice without having to work around the behavior of one or the other. Obviously this is becoming a recurring theme, but let me chew on this one a bit while I work on some of the more immediate items on the backlog.

[Jonathan Toland]

For reference my project uses three source roots: src, resource-bundles, and raw-src, which contains Jade/Stylus/CoffeeScript files that generate my Lightning components.

[Scott Wells]

Between allowing resource bundles in another source root and the upcoming directory structure flexibility afforded by Salesforce DX, I think this overall concern is probably addressed. Please let me know if not.