It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Hi guys, i try run latest version from SDK
atlas-run-standalone --product jira --version 8.5.0 or 8.4.0

And I receive have error

[INFO] [2.ContainerStartMojo] Resolved container artifact org.codehaus.cargo:cargo-core-container-tomcat:jar:1.6.10 for container tomcat8x
[INFO] [talledLocalContainer] Tomcat 8.x starting...
[DEBUG] [neLocalConfiguration] Setting property [cargo.java.home] = [C:\Program Files (x86)\Java\jdk1.8.0_192\jre]
[DEBUG] [neLocalConfiguration] Searching properties for Resource definitions
[DEBUG] [neLocalConfiguration] Searching properties for DataSource definitions
[DEBUG] [neLocalConfiguration] Found DataSource definition: value [cargo.datasource.url=jdbc:h2:file:C:/Applications/JIRA/amps-standalone-jira-8.5.0/target/jira/home/database/h2db|cargo.datasource.driver=org.h2.Driver|cargo.datasource.username=sa|cargo.datasource.password=|cargo.datasource.jndi=jdbc/JiraDS]
[DEBUG] [neLocalConfiguration] Searching properties for User definition
[DEBUG] [neLocalConfiguration] Found User definition: value [admin::manager-script]
[INFO] [stalledLocalDeployer] Deploying [C:\Applications\JIRA\amps-standalone-jira-8.5.0\target\jira\jira.war] to [C:\Applications\JIRA\amps-standalone-jira-8.5.0/target\container\tomcat8x\cargo-jira-home\webapps]...
[DEBUG] [neLocalConfiguration] Setting property [cargo.tomcat.httpSecure] = [false]
[DEBUG] [talledLocalContainer] Connection attempt with socket Socket[unconnected], current time is 1572355731248
[DEBUG] [talledLocalContainer] Socket Socket[unconnected] for port 8009 closed
[DEBUG] [talledLocalContainer] Connection attempt with socket Socket[unconnected], current time is 1572355733321
[DEBUG] [talledLocalContainer] Socket Socket[unconnected] for port 52880 closed
[DEBUG] [talledLocalContainer] Connection attempt with socket Socket[unconnected], current time is 1572355735383
[DEBUG] [talledLocalContainer] Socket Socket[unconnected] for port 2990 closed
[DEBUG] [URLDeployableMonitor] Checking URL [http://localhost:2990/cargocpc/index.html] for status using a timeout of [600000] ms...
[DEBUG] [URLDeployableMonitor] URL [http://localhost:2990/cargocpc/index.html] is not responding: -1 java.net.ConnectException: Connection refused: connect
...
[DEBUG] [URLDeployableMonitor] Notifying monitor listener [org.codehaus.cargo.container.spi.deployer.DeployerWatchdog@ea78f0]
[INFO] [yer.DeployerWatchdog] Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
[WARNING] [talledLocalContainer] org.codehaus.cargo.container.ContainerException: Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
[ERROR] Starting container [org.codehaus.cargo.container.tomcat.Tomcat8xInstalledLocalContainer@89fc44] failed, now stopping container
[INFO] [talledLocalContainer] Tomcat 8.x is stopping...
[DEBUG] [talledLocalContainer] Socket Socket[unconnected] for port 2990 closed
[DEBUG] [talledLocalContainer] Port 2990 is shutdown
[INFO] [talledLocalContainer] Tomcat 8.x is stopped
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11:12 min
[INFO] Finished at: 2019-10-29T15:39:07+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.atlassian.maven.plugins:amps-maven-plugin:8.0.2:run-standalone (default-cli) on project standalone-pom: Cannot start container [org.codehaus.cargo.container.tomcat.Tomcat8xInstalledLocalContainer@89fc44]: Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.atlassian.maven.plugins:amps-maven-plugin:8.0.2:run-standalone (default-cli) on project standalone-pom: Cannot start container [org.codehaus.cargo.container.tomcat.Tomcat8xInstalledLocalContainer@89fc44]
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot start container [org.codehaus.cargo.container.tomcat.Tomcat8xInstalledLocalContainer@89fc44]
at com.atlassian.maven.plugins.amps.RunStandaloneMojo.doExecute (RunStandaloneMojo.java:76)
at com.atlassian.maven.plugins.amps.AbstractProductHandlerMojo.execute (AbstractProductHandlerMojo.java:754)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot start container [org.codehaus.cargo.container.tomcat.Tomcat8xInstalledLocalContainer@89fc44]
at org.codehaus.cargo.maven2.ContainerStartMojo.doExecute (ContainerStartMojo.java:74)
at org.codehaus.cargo.maven2.AbstractCargoMojo.execute (AbstractCargoMojo.java:471)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojo (MojoExecutor.java:119)
at com.atlassian.maven.plugins.amps.util.MojoUtils.execute (MojoUtils.java:36)
at com.atlassian.maven.plugins.amps.MavenGoals.startWebapp (MavenGoals.java:972)
at com.atlassian.maven.plugins.amps.product.AbstractWebappProductHandler.startApplication (AbstractWebappProductHandler.java:63)
at com.atlassian.maven.plugins.amps.product.AbstractProductHandler.start (AbstractProductHandler.java:90)
at com.atlassian.maven.plugins.amps.RunMojo.startProducts (RunMojo.java:137)
at com.atlassian.maven.plugins.amps.RunMojo.doExecute (RunMojo.java:84)
at com.atlassian.maven.plugins.amps.AbstractProductHandlerMojo.execute (AbstractProductHandlerMojo.java:754)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojo (MojoExecutor.java:119)
at com.atlassian.maven.plugins.amps.util.MojoUtils.execute (MojoUtils.java:36)
at com.atlassian.maven.plugins.amps.util.MojoUtils.executeWithMergedConfig (MojoUtils.java:66)
at com.atlassian.maven.plugins.amps.MavenGoals.executeAmpsRecursively (MavenGoals.java:176)
at com.atlassian.maven.plugins.amps.RunStandaloneMojo.doExecute (RunStandaloneMojo.java:74)
at com.atlassian.maven.plugins.amps.AbstractProductHandlerMojo.execute (AbstractProductHandlerMojo.java:754)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: org.codehaus.cargo.container.ContainerException: Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
at org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watch (DeployerWatchdog.java:111)
at org.codehaus.cargo.container.spi.AbstractLocalContainer.waitForCompletion (AbstractLocalContainer.java:385)
at org.codehaus.cargo.container.spi.AbstractLocalContainer.start (AbstractLocalContainer.java:232)
at org.codehaus.cargo.maven2.ContainerStartMojo.executeLocalContainerAction (ContainerStartMojo.java:84)
at org.codehaus.cargo.maven2.ContainerStartMojo.doExecute (ContainerStartMojo.java:58)
at org.codehaus.cargo.maven2.AbstractCargoMojo.execute (AbstractCargoMojo.java:471)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojo (MojoExecutor.java:119)
at com.atlassian.maven.plugins.amps.util.MojoUtils.execute (MojoUtils.java:36)
at com.atlassian.maven.plugins.amps.MavenGoals.startWebapp (MavenGoals.java:972)
at com.atlassian.maven.plugins.amps.product.AbstractWebappProductHandler.startApplication (AbstractWebappProductHandler.java:63)
at com.atlassian.maven.plugins.amps.product.AbstractProductHandler.start (AbstractProductHandler.java:90)
at com.atlassian.maven.plugins.amps.RunMojo.startProducts (RunMojo.java:137)
at com.atlassian.maven.plugins.amps.RunMojo.doExecute (RunMojo.java:84)
at com.atlassian.maven.plugins.amps.AbstractProductHandlerMojo.execute (AbstractProductHandlerMojo.java:754)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojo (MojoExecutor.java:119)
at com.atlassian.maven.plugins.amps.util.MojoUtils.execute (MojoUtils.java:36)
at com.atlassian.maven.plugins.amps.util.MojoUtils.executeWithMergedConfig (MojoUtils.java:66)
at com.atlassian.maven.plugins.amps.MavenGoals.executeAmpsRecursively (MavenGoals.java:176)
at com.atlassian.maven.plugins.amps.RunStandaloneMojo.doExecute (RunStandaloneMojo.java:74)
at com.atlassian.maven.plugins.amps.AbstractProductHandlerMojo.execute (AbstractProductHandlerMojo.java:754)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

 

I installed SDK Version 8.0.16, yes i read this version support Jira Server 7.6.1 - 8.2.1.

Howe I can run latest version of JIRA

3 answers

1 accepted

0 votes
Answer accepted
Andy Heinzer Atlassian Team Nov 05, 2019

Hi @Денис Алексеенко -Nik ADA- 

Thanks for posting the output of that command. Something in your results stuck out for me, specifically:

runtime: C:\Program Files (x86)

and

arch: "x86"

which makes it look like the Oracle Java is using the x86 distribution (this is a 32 bit Java version). However Atlassian recently deprecated support for the 32-bit installers from Jira 8.1 (and completely removed them starting with 8.2).  More details in https://confluence.atlassian.com/adminjiraserver081/end-of-support-announcements-970608506.html

I believe that since the SDK is updated to be able to deploy the latest versions (8.5 today), that all the Jira 8.x versions might all be affected by this in the SDK.  Whereas the older Jira 7 and previous versions would still have some support for 32 bit (x86) Java JVMs.

I would be interested to see if you can instead install a 64-bit version of Java, point to that directory for the JAVA_HOME variable, restart windows to make this setting take affect, and then see if you can recreate this problem with the SDK.  The example output of that same command that we have over in https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-windows-system/ does show a 64 bit for both java and OS arch:

Java home: C:\Program Files\Java\jdk1.8.0_91\jre
Default locale: en_AU, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"

In my opinion the documentation on https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-windows-system/ likely needs to be updated in order to reflect this changing need and to be more explicit in the expectation to use a 64 bit Java for developing in Jira 8 and higher.  However if you believe that you still need to be using the 32-bit JVM here for a Jira 8.0.0, please let me know if you have some use case here and I can look into this problem further.

Thanks,

Andy

Thanks Andy for the answer, I installed Java 64-bit version

C:\Applications\JIRA>atlas-version

ATLAS Version: 8.0.16
ATLAS Home: C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16
ATLAS Scripts: C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16\bin
ATLAS Maven Home: C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16\apache-maven-3.5.4
AMPS Version: 8.0.2
--------
Executing: "C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16\apache-maven-3.5.4\bin\mvn.cmd" --version -gs C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16\apache-maven-3.5.4/conf/settings.xml
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T21:33:14+03:00)
Maven home: C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16\apache-maven-3.5.4\bin\..
Java version: 1.8.0_192, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_192\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Yes, it helped.
I agree with you that it is worth updating the information on the pages https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-windows-system/ or providing additional information about this.

0 votes
Andy Heinzer Atlassian Team Oct 30, 2019

Hi,

Sorry to hear that there appears to be a problem with launching Jira from the SDK here.  I can see that you are using a windows machine to use the SDK here.  I tried to replicate this problem from my MAC, and at least so far in the unix/linux version of the same SDK version I have not yet been able to replicate this problem.

I would be interested to see what the output is from your system when you run the command

atlas-version

I'd also be interested to see if potentially you get a different result if you were to first open the command prompt (cmd.exe) and Run as Administrator.  I have seen that in some Windows environments, new features like UAC and alike can cause commands run from the command prompt to not have all the permissions needed.   Whereas using the Run as administrator option to first open that command prompt can sometimes grant those commands the needed rights before launching this sdk command.

Additionally I would want to make sure that you are following the setup guide in Install the Atlassian SDK on a Windows system.

Try this and let me the know the results.  If this doesn't help, I'd like to learn more about your operating system environment, such as which version of Windows this is and the output of the atlas-version command on your system.

Thanks

Andy

atlas-version return this information:

C:\Applications\JIRA>atlas-version

ATLAS Version: 8.0.16
ATLAS Home: C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16
ATLAS Scripts: C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16\bin
ATLAS Maven Home: C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16\apache-maven-3.5.4
AMPS Version: 8.0.2
--------
Executing: "C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16\apache-maven-3.5.4\bin\mvn.cmd" --version -gs C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16\apache-maven-3.5.4/conf/settings.xml
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T21:33:14+03:00)
Maven home: C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.16\apache-maven-3.5.4\bin\..
Java version: 1.8.0_192, vendor: Oracle Corporation, runtime: C:\Program Files (x86)\Java\jdk1.8.0_192\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "x86", family: "windows"

 

  • About setup guide in Install the Atlassian SDK
    Yes I do the same steps, and I can run JIRA version 7.13.9 from comand
    atlas-run-standalone --product jira --version 7.13.9 
    start from version 8.0.0 I can't run
  • command prompt I run always as Administrator

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

303 views 1 3
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you