Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

SDK 8.0.X Does not work on Windows

Zach Mitchell
Contributor
February 26, 2019

Anyone having any luck getting the new SDK's to work on Windows, i noticed that in the batch files they are using linux style variabless "${variable}" which does not process and thus needs to be removed from the batch prior to running. But even after that when i update my pom.xml to include the new amps version (8.0.0) and the naming change form "maven-confluence-plugin" to "confluence-maven-plugin" it still will not allow me to perform atlas-version or atlas-run.

output of atlas-version -e

ATLAS Version: 8.0.7
ATLAS Home: C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.7
ATLAS Scripts: C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.7\bin
ATLAS Maven Home: C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.7\apache-maven-3.5.4
AMPS Version: 8.0.0
--------
'else' is not recognized as an internal or external command,
operable program or batch file.
Executing: "C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.7\apache-maven-3.5.4\bin\mvn.cmd" -gs C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.7\apache-maven-3.5.4/conf/settings.xml -e
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.238 s
[INFO] Finished at: 2019-02-26T10:24:30-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initializ
e, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, packa
ge, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
org.apache.maven.lifecycle.NoGoalSpecifiedException: No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Availa
ble lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, proce
ss-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy.
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:97)
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] Re-run Maven using the -X switch to enable full debug logging.
[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/NoGoalSpecifiedException

 

If i switch back to the 6.3.12 SDK, package and run i have no issues. Are Linux users having this issue or just windows?

 

3 answers

1 vote
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 14, 2020

Hi all,

This is a bug in the SDK that is commonly found in Windows environments.  We documented this problem over in https://ecosystem.atlassian.net/browse/ATLASSDK-93

The good news is that this appears to be fixed in the 8.0.17, however this version has not yet be released as of today.  In the meantime, other users in related threads, such as https://community.atlassian.com/t5/Jira-questions/Re-Re-Unknown-lifecycle-phase-error/qaq-p/1047020/comment-id/335142#M335142 have documented a work-around to this problem.   From Vlad on that thread:

Looks like I was able to fix "Lifecycle Phase" error as follows (I got it on Windows):

1. In "atlas-mvn.bat" file comment out the following line:

call set MVN_COMMAND=%%MVN_COMMAND:${mavenPluginName}=%MVN_PLUGIN%%%

2. Replace it with:

call set MVN_COMMAND=%%MVN_COMMAND:%%

Vlad

I hope this helps.

Andy

Andrew S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 14, 2020

The 8.0.17 release is in progress.

1 vote
Marcin Olszewski
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 17, 2019

set ATLAS_MVN=C:\Applications\Atlassian\atlassian-plugin-sdk-8.0.7\apache-maven-3.5.4\bin\mvn.cmd

and fix "/" character to "\" because it is hardcoded in .bat files

0 votes
Stephen Sifers
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 27, 2019

Hello Zach,

Something to be aware of is this is a support community and not often browsed by developers. We want to ensure you get the responses and answers you need so we would suggest you check out the Developer Community. The Developer Community may have more available resources to answer or address your developer questions.

Regards,
Stephen Sifers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events