[
https://issues.apache.org/jira/browse/CB-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401698#comment-13401698
]
Tim Kim commented on CB-962:
----------------------------
Oh - okie dokie:
Try now:
https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-blackberry-webworks.git;a=commit;h=25acb0ee92aa54a5b8be44ee201308315bfd28ba
Your recommendation seems to work with the create/ant scripts now.
> Building BB sample project fails
> --------------------------------
>
> Key: CB-962
> URL: https://issues.apache.org/jira/browse/CB-962
> Project: Apache Cordova
> Issue Type: Bug
> Components: BlackBerry
> Affects Versions: 1.9.0
> Reporter: Drew Walters
> Assignee: Tim Kim
> Priority: Critical
>
> The change to add the debug flag to the build has broken the build of the
> sample project on my Mac:
> build:
> [exec] [INFO] Parsing command line options
> [exec] [ERROR] Invalid command line parameters
> [exec] bbwp version 2.3.1.5 Copyright(C) 2010-2011 Research In
> Motion
> [exec]
> http://www.blackberry.com/developers/webworkssdk/
> [exec]
> [exec] bbwp [drive:][path]archive [-s [dir]] [-g [password]] [-o dir]
> [exec]
> [exec] archive Specifies the .zip file to compile
> [exec] -s Save source. The default behaviour is
> to not save the source files. If dir is specified then creates dir\src\
> directory structure. If no dir specified then the path of archive is assumed
> [exec] -g Sign the .cod file after compilation
> using password. If both -g and password are not present then the .cod will
> not be signed. If -g is present and password is not, Signature Tool will
> prompt for entering password
> [exec] -o Redirects output file location to dir
> (.cod, .alx, .jad). If both -o and dir are not specified then the path of
> archive is assumed
> [exec] -v Turn on verbose messages
> [exec] -d Enables Web Inspector on 7.0+ OS
> [exec] -h Display this usage information
> [exec]
> [exec]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
