Skip to content
This repository

Typing "bbwp -V" always prints out version 1.0.0.0 #126

Open
ishneur opened this Issue May 03, 2012 · 8 comments

5 participants

Igor Shneur Nukul Bhasin James Keshavarzi Ken Wallis Ken Whatmough
Igor Shneur
ishneur commented May 03, 2012

Description:

When I use SCM build "BlackBerry 10 WebWorks SDK 1.0.0.7" and type "bbwp -V" at the command prompt, it prints out version 1.0.0.0.

The same happens with previous SCM builds.

Nukul Bhasin
nukulb commented May 04, 2012

@ronalag - we should probably tie this to the same version number that is coming from maven. Might take some thinking though since it might be hardcoded in the packager.
@jkeshavarzi - how does the packager get this version number?

James Keshavarzi
Nukul Bhasin
nukulb commented May 06, 2012

if that is true then if I can bbwp -V where is it getting the version number from because it return 1.0.0.0 but the SCM build has a version number 1.0.0.7?
am I missing something?

Nukul Bhasin
nukulb commented May 06, 2012

if that is true then if I can bbwp -V where is it getting the version number from because it return 1.0.0.0 but the SCM build has a version number 1.0.0.7?
am I missing something?

James Keshavarzi

The version number i was referring to earlier is in the productization repo [build.bat] and is used by SCM.
The version number in the packager that shows when you type bbwp -V is in the command-line code and is in fact hard coded to 1.0.0.0 (see below).

cmd
.version('1.0.0.0')
.usage('[drive:][path]archive [-s [dir]] [[ -g genpassword] [-buildId num]] [-o dir] [-d]')
.option('-s, --source [dir]', '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')
.option('-g, --password ', 'Signing key password')
.option('-buildId ', '[deprecated] Use --buildId.')
.option('-b, --buildId ', 'Specifies the build number for signing (typically incremented from previous signing).')
.option('-o, --output ', 'Redirects output file location to dir. If both -o and dir are not specified then the path of archive is assumed')
.option('-d, --debug', 'Allows use of not signed build on device by utilizing debug token and enables Web Inspector.')
.option('-v, --verbose', 'Turn on verbose messages');

Nukul Bhasin
nukulb commented May 06, 2012

that makes sense, so now we need to find a way to turn on the -v version number to return the same version number as the scm build. We will take it up when it becomes priority, right now @kwallis needs to decide priority. I think it will become priority once Ripple gets affected by it since Ripple B&D just simply calls the command line and reads the output.

Ken Wallis
Owner
kwallis commented May 09, 2012

cc @kwhatmough @dansilivestru I don't believe that Ripple actually ever uses this version?

Ken Whatmough

Correct. But potentially in the future it's possible that Build and Deploy might want to know which version of the SDK it is pointing to. But today, no.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.