Make our build configs more portable by using the default src config

If a `src` config is not provided, by default, all of the library sources are included.  There is some special handling in the build task to make sure all library sources are included regardless of the path to the build config.  When someone includes a `src` config, path patterns are assumed to be relative to the current working directory (unless overriden with the `cwd` config).  So, when you use the `src` config, your config is no longer portable.
This commit is contained in:
Tim Schaub
2014-07-14 17:52:10 -06:00
parent 4aa76977d2
commit aecaa52cb1
5 changed files with 1 additions and 5 deletions
-1
View File
@@ -1,6 +1,5 @@
{
"exports": ["*"],
"src": ["src/**/*.js"],
"compile": {
"externs": [
"externs/bingmaps.js",
-1
View File
@@ -1,6 +1,5 @@
{
"exports": ["*"],
"src": ["src/**/*.js"],
"compile": {
"externs": [
"externs/bingmaps.js",
-1
View File
@@ -1,6 +1,5 @@
{
"exports": ["*"],
"src": ["src/**/*.js"],
"compile": {
"externs": [
"externs/bingmaps.js",
-1
View File
@@ -1,6 +1,5 @@
{
"exports": ["*"],
"src": ["src/**/*.js"],
"compile": {
"externs": [
"externs/bingmaps.js",