trouble installing standalone

[Colin Mason]

I am attempting to run the standalone JIRA app on my local machine for development using the command line (

atlas-run-standalone --product jira) as defined in the page: https://developer.atlassian.com/display/DOCS/Explore+the+Installed+SDK+and+the+atlas+Commands

It keeps failing.  I'm running Windows 7 64-bit on a Dell engineering-level laptop.

Here are the errors I'm getting:

[INFO] [yer.DeployerWatchdog] Deployable [http://localhost:2990/cargocpc/index.h
tml] failed to finish deploying within the timeout period [600000]. The Deployab
le state is thus unknown.
[WARNING] [talledLocalContainer] org.codehaus.cargo.container.ContainerException
: Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploy
ing within the timeout period [600000]. The Deployable state is thus unknown.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17:45 min
[INFO] Finished at: 2014-11-06T08:28:05-06:00
[INFO] Final Memory: 16M/108M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-amps-plugin:5.0
.4:run-standalone (default-cli) on project standalone-pom: Unable to execute moj
o: Execution null of goal org.codehaus.cargo:cargo-maven2-plugin:1.4.7:start fai
led: Deployable [http://localhost:2990/cargocpc/index.html] failed to finish dep
loying within the timeout period [600000]. The Deployable state is thus unknown.
-> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
xception
C:\atlastutorial>

Here is the log file:

Nov 06, 2014 9:39:18 AM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [C:\atlastutorial\amps-standalone\target\container\tomcat7x\cargo-jira-home\common\classes], exists: [false], isDirectory: [false], canRead: [false]
Nov 06, 2014 9:39:20 AM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [C:\atlastutorial\amps-standalone\target\container\tomcat7x\cargo-jira-home\shared\classes], exists: [false], isDirectory: [false], canRead: [false]
Nov 06, 2014 9:39:20 AM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [C:\atlastutorial\amps-standalone\target\container\tomcat7x\cargo-jira-home\shared\lib], exists: [false], isDirectory: [false], canRead: [false]

[Jeff Lane]

I had/have this same problem (Windows 10, Surface Pro 3). I assume that there might be more than one explanation, but for me the problem was related to the file location where I was running the command. In my case I was running the command from a working directory on a mounted micoSD card (the volume is mounted to a folder location without a drive letter assigned). However, when I execute the command from a folder location on the C: drive, it works fine. Obviously, I wouldn't expect this behavior on Linux, but there you have it.