search

kitsonk / dojo-node-boilerplate

A quickstart "template" for using the Dojo Toolkit on NodeJS
Other
16 stars 10 forks source link

Cannot build application #3

Open IIIEII opened 11 years ago

IIIEII commented 11 years ago

I have troubles building cloned (unmodified) application. Here is some additional information:

$ uname -a Linux ubuntu 2.6.32-46-generic #108-Ubuntu SMP Thu Apr 11 15:55:01 UTC 2013 i686 GNU/Linux $ node --version v0.10.4 $ git clone --recursive https://github.com/kitsonk/dojo-node-boilerplate.git $ cd dojo-node-boilerplate $ ./build.sh processing profile resource /home/iiieii/nodejs/dojo-node-boilerplate/app.profile.js info(107) Package Version: package: dojo; version: 1.8.3 processing profile resource /home/iiieii/nodejs/dojo-node-boilerplate/src/dojo/dojo.profile.js info(107) Package Version: package: app; version: 1.0.0 processing profile resource /home/iiieii/nodejs/dojo-node-boilerplate/src/app/package.js info(107) Package Version: package: app-client; version: 1.0.0 processing profile resource /home/iiieii/nodejs/dojo-node-boilerplate/src/app-client/package.js discovering resources... starting reading resources... starting processing raw resource content... starting tokenizing resource... starting processing resource tokens... starting parsing resource... { [Error: spawn ENOENT] code: 'ENOENT', errno: 'ENOENT', syscall: 'spawn' } Error: spawn ENOENT at errnoException (child_process.js:975:11) at Process.ChildProcess._handle.onexit (child_process.js:766:34)

kitsonk commented 11 years ago

Do you have Java installed and available? The profile that is included in the repository optimises the client side code using Google Closure which requires Java.

Here is what I am getting when I do a build...

$ ./build.sh
processing profile resource /Users/kitsonk/github/dojo-node-boilerplate/app.profile.js
info(107) Package Version: package: dojo; version: 1.9.0
processing profile resource /Users/kitsonk/github/dojo-node-boilerplate/src/dojo/dojo.profile.js
info(107) Package Version: package: app; version: 1.0.0
processing profile resource /Users/kitsonk/github/dojo-node-boilerplate/src/app/package.js
info(107) Package Version: package: app-client; version: 1.0.0
processing profile resource /Users/kitsonk/github/dojo-node-boilerplate/src/app-client/package.js
discovering resources...
starting reading resources...
starting processing raw resource content...
starting tokenizing resource...
starting processing resource tokens...
starting parsing resource...
starting processing resource AST...
warn(216) dojo/has plugin resource could not be resolved during build-time. plugin resource id: dom-addeventlistener?:./aspect; reference module id: dojo/on
warn(224) A plugin dependency was encountered but there was no build-time plugin resolver. module: dojo/request; plugin: dojo/request/default
warn(224) A plugin dependency was encountered but there was no build-time plugin resolver. module: dojo/request/node; plugin: dojo/node
warn(224) A plugin dependency was encountered but there was no build-time plugin resolver. module: dojo/request/node; plugin: dojo/node
warn(224) A plugin dependency was encountered but there was no build-time plugin resolver. module: dojo/request/node; plugin: dojo/node
warn(224) A plugin dependency was encountered but there was no build-time plugin resolver. module: dojo/request/node; plugin: dojo/node
warn(224) A plugin dependency was encountered but there was no build-time plugin resolver. module: dojo/request/registry; plugin: dojo/request/default
warn(216) dojo/has plugin resource could not be resolved during build-time. plugin resource id: host-browser?dom-addeventlistener?:../on:; reference module id: dojo/request/watch
starting executing global optimizations...
starting writing resources...
starting cleaning up...
waiting for the optimizer runner to finish...
starting reporting...
Report written to /Users/kitsonk/github/dojo-node-boilerplate/lib/build-report.txt
Process finished normally.
    errors: 0
    warnings: 8
    build time: 65.965 seconds
kitsonk commented 11 years ago

Actually, I know what the issue is. There is an issue with the builder under node in 1.8.3. I have upgraded the repository to Dojo 1.9.0 and that should fix the issue.