search

RC-Paves3-build / plovr

Automatically exported from code.google.com/p/plovr
0 stars 0 forks source link

"inputs" and "paths" params are config-file relative while "closure-library" param is relative to execution directory #13

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
a project with the following layout:

projectdir/
  closure-library/
  subproject-1/
    config.js
    app.js
  subproject-2/
    config.js
    app.js
  shared-subproject/
    shared.js

If I execute plovr serve from projectdir then I need a config file for app 1 
that looks, oddly, like so:

    "inputs": "./app.js", 
    "paths": ["../shared-subproject/"],
    "closure-library" : "./closure-library/closure/goog/"

where "inputs" and "paths" are relative to the location of the project config, 
but where the closure-library param is relative to the current directory I'm 
executing plovr from.

Original issue reported on code.google.com by andydun...@gmail.com on 12 Oct 2010 at 5:51

GoogleCodeExporter commented 8 years ago 
a project with the following layout:

projectdir/
  closure-library/
  subproject-1/
    config.js
    app.js
  subproject-2/
    config.js
    app.js
  shared-subproject/
    shared.js

If I execute plovr serve from projectdir then I need a config file for app 1 
that looks, oddly, like so:

    "inputs": "./app.js", 
    "paths": ["../shared-subproject/"],
    "closure-library" : "./closure-library/closure/goog/"

where "inputs" and "paths" are relative to the location of the project config, 
but where the closure-library param is relative to the current directory I'm 
executing plovr from.

Original comment by andydun...@gmail.com on 12 Oct 2010 at 5:51

GoogleCodeExporter commented 8 years ago 
Fixed in changeset 2de3b86b59: 
http://code.google.com/p/plovr/source/detail?r=2de3b86b59d5cab44c0a1d5631d9ff8f1
c61f6ae

Original comment by bolinf...@gmail.com on 14 Oct 2010 at 4:41