When using an output path that is relative (-o myOutputFolder), packager throws an error (see below).
I have already fixed this issue in next-fixRelativeOutputPaths. I am creating this, so it can be verified and closed by SV&V.
C:\BB10-Webworks-Packager>"C:\BB10-Webworks-Packager\dependencies\node\node.exe"
"C:\BB10-Webworks-Packager\lib\bbwp.js" C:\sampleApp\testTemplate0202.zip -o my
Out -s
16:50:05 - INFO - Populating application source
16:50:05 - INFO - Parsing config.xml
16:50:05 - INFO - Generating output files
16:50:05 - ERROR - { [Error: ENOENT, no such file or directory 'C:\BB10-Webworks
-Packager\myOut\src\myOut\src\chrome']
errno: 34,
code: 'ENOENT',
path: 'C:\BB10-Webworks-Packager\myOut\src\myOut\src\chrome',
syscall: 'stat' }
When using an output path that is relative (-o myOutputFolder), packager throws an error (see below). I have already fixed this issue in next-fixRelativeOutputPaths. I am creating this, so it can be verified and closed by SV&V.
C:\BB10-Webworks-Packager>"C:\BB10-Webworks-Packager\dependencies\node\node.exe" "C:\BB10-Webworks-Packager\lib\bbwp.js" C:\sampleApp\testTemplate0202.zip -o my Out -s 16:50:05 - INFO - Populating application source 16:50:05 - INFO - Parsing config.xml 16:50:05 - INFO - Generating output files 16:50:05 - ERROR - { [Error: ENOENT, no such file or directory 'C:\BB10-Webworks -Packager\myOut\src\myOut\src\chrome'] errno: 34, code: 'ENOENT', path: 'C:\BB10-Webworks-Packager\myOut\src\myOut\src\chrome', syscall: 'stat' }