Unable to run atlas-run-standalone: mvn complains about unrecognized option --product

[Mitchell Im]

I'm following the instructions for setting up a Jira development environment (https://developer.atlassian.com/display/DOCS/Explore+the+Installed+SDK+and+the+atlas+Commands), but hit this issue where the options passed to mvn fail. What's going on?

C:\dir>atlas-run-standalone --product jira --version 5.2.4
Executing: "C:\Users\me\Documents\atlassian-plugin-sdk\apache-maven\bin\mvn.bat" com.atlassian.maven.plugins:maven-amps-plugin:4.2.1:run-standalone -gs C:\Users\me\Documents\atlassian-plugin-sdk\apache-maven/conf/settings.xml --product jira
Unable to parse command line options: Unrecognized option: --product

usage: mvn [options] [<goal(s)>] [<phase(s)>]

Options:
 -q,--quiet                        Quiet output - only show errors
 -C,--strict-checksums             Fail the build if checksums don't match
 -c,--lax-checksums                Warn if checksums don't match
 -P,--activate-profiles            Comma-delimited list of profiles to
                                   activate
 -amd,--also-make-dependents       If project list is specified, also
                                   build projects that depend on projects on the
 list
 -ff,--fail-fast                   Stop at first failure in reactorized
                                   builds
 -rf,--resume-from                 Resume reactor from specified project
 -fae,--fail-at-end                Only fail the build afterwards; allow
                                   all non-impacted builds to continue
 -B,--batch-mode                   Run in non-interactive (batch) mode
 -am,--also-make                   If project list is specified, also
                                   build projects required by the list
 -fn,--fail-never                  NEVER fail the build, regardless of
                                   project result
 -emp,--encrypt-master-password    Encrypt master security password
 -ep,--encrypt-password            Encrypt server password
 -up,--update-plugins              Synonym for cpu
 -N,--non-recursive                Do not recurse into sub-projects
 -npr,--no-plugin-registry         Don't use ~/.m2/plugin-registry.xml for
                                   plugin versions
 -gs,--global-settings             Alternate path for the global settings
                                   file
 -U,--update-snapshots             Forces a check for updated releases and
                                   snapshots on remote repositories
 -cpu,--check-plugin-updates       Force upToDate check for any relevant
                                   registered plugins
 -npu,--no-plugin-updates          Suppress upToDate check for any
                                   relevant registered plugins
 -V,--show-version                 Display version information WITHOUT
                                   stopping build
 -D,--define                       Define a system property
 -X,--debug                        Produce execution debug output
 -e,--errors                       Produce execution error messages
 -f,--file                         Force the use of an alternate POM file.
 -h,--help                         Display help information
 -o,--offline                      Work offline
 -pl,--projects                    Build specified reactor projects
                                   instead of all projects
 -r,--reactor                      Dynamically build reactor from
                                   subdirectories
 -s,--settings                     Alternate path for the user settings
                                   file
 -v,--version                      Display version information

[Torsten Weck · Accepted solution]

try: atlas-run-standalone -Dproduct=jira

[Inseok Lee]

Thanks a lot

[Mitchell Im]

Yup. That does it.

But seriously? The documentation's wrong on that? As one of the initial steps you're supposed to follow?

Fwiw, atlas-run did start Tomcat + Jira properly, so I wasn't blocked, but... seriously....

[Inseok Lee]

It seems solved after upgrade Atlassin SDK. I reinstalled 4.2.1 to 4.2.2. and I can use its command well

[Mitchell Im]

And since somebody's bound to ask:

C:\Users\me>atlas-version

ATLAS Version:    4.2.1
ATLAS Home:       C:\Users\me\Documents\atlassian-plugin-sdk
ATLAS Scripts:    C:\Users\me\Documents\atlassian-plugin-sdk\bin
ATLAS Maven Home: C:\Users\me\Documents\atlassian-plugin-sdk\apache-maven
--------
Executing: "C:\Users\me\Documents\atlassian-plugin-sdk\apache-maven\bin\mvn
.bat" --version -gs C:\Users\me\Documents\atlassian-plugin-sdk\apache-maven/conf/settings.xml
Apache Maven 2.1.0 (r755702; 2009-03-18 12:10:27-0700)
Java version: 1.7.0_21
Java home: C:\Program Files\Java\jdk1.7.0_21\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"