Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Error running atlas-run-standalone due to missing POM

Ben Sheppard November 19, 2014

I've been going through the Atlassian Plugin SDK walkthrough from the beginning, and did not skip any steps. I'm at the Explore the Installed SDK and Atlas Commands section, and when trying to do the "atlas-run-standalone – product jira" step I'm getting the following error. (I went back and added the "-e" command to get the full stack trace in case that will help any.

I double checked with my system administrator that we do not need an HTTP proxy, even though I don't think this would have anything to do with my error.

 

C:\atlastutorial>atlas-run-standalone -e -- product jira
Executing: "C:\Users\jbs\atlassian-plugin-sdk\apache-maven-3.2.1\bin\mvn.bat" co
m.atlassian.maven.plugins:maven-amps-plugin:5.0.4:run-standalone -gs C:\Users\jb
s\atlassian-plugin-sdk\apache-maven-3.2.1/conf/settings.xml -e -- product jira
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.071 s
[INFO] Finished at: 2014-11-19T10:12:56-05:00
[INFO] Final Memory: 4M/243M
[INFO] ------------------------------------------------------------------------
[ERROR] The goal you specified requires a project to execute but there is no POM
 in this directory (C:\atlastutorial). Please verify you invoked Maven from the
correct directory. -> [Help 1]
org.apache.maven.lifecycle.MissingProjectException: The goal you specified requi
res a project to execute but there is no POM in this directory (C:\atlastutorial
). Please verify you invoked Maven from the correct directory.
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
eStarter.java:80)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
cher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
a:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
uncher.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 rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProject
Exception

3 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

3 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 19, 2014

You need to have a pom.xml to run the project.

I usually go for 

atlas-create-plugin (and give it a name for the project, like mylittleplugin)

cd mylittleplugin

atlas-run-standalone

Ben Sheppard November 19, 2014

What directory do I have to do that in? I tried it in C:\atlastutorial and got another BUILD FAILURE. c:\atlastutorial>atlas-create-plugin mylittleplugin Executing: "C:\Users\jbs\atlassian-plugin-sdk\apache-maven-3.2.1\bin\mvn.bat" co m.atlassian.maven.plugins:maven-amps-plugin:5.0.4:create -gs C:\Users\jbs\atlass ian-plugin-sdk\apache-maven-3.2.1/conf/settings.xml mylittleplugin [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.072 s [INFO] Finished at: 2014-11-19T12:02:44-05:00 [INFO] Final Memory: 5M/243M [INFO] ------------------------------------------------------------------------ [ERROR] The goal you specified requires a project to execute but there is no POM in this directory (c:\atlastutorial). Please verify you invoked Maven from the correct directory. -> [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/MissingProject Exception c:\atlastutorial>

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 19, 2014

No, you have to run the atlas-create-plugin and answer its questions, not just add a parameter

Ben Sheppard November 19, 2014

Excellent. Thank you. I got the project created, but ran into another error. I'm assuming I should create another question for that one?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 19, 2014

No harm in asking here ;-)

Ben Sheppard November 20, 2014

Sorry for the delay in getting back. There's a limit of 3 questions/answers/comments in 24 hours for new users. Alright, thanks. Here's what I did next after creating the project. (I wasn't sure what ID was for which, so I just called it artId) C:\atlastutorial\artId>atlas-run-standalone Executing: "C:\Users\jbs\atlassian-plugin-sdk\apache-maven-3.2.1\bin\mvn.bat" co m.atlassian.maven.plugins:maven-amps-plugin:5.0.4:run-standalone -gs C:\Users\jb s\atlassian-plugin-sdk\apache-maven-3.2.1/conf/settings.xml [INFO] Scanning for projects... Downloading: https://maven.atlassian.com/repository/public/com/atlassian/maven/p lugins/maven-refapp-plugin/5.0.4/maven-refapp-plugin-5.0.4.pom Downloaded: https://maven.atlassian.com/repository/public/com/atlassian/maven/pl ugins/maven-refapp-plugin/5.0.4/maven-refapp-plugin-5.0.4.pom (2 KB at 2.0 KB/se c) Downloading: https://maven.atlassian.com/repository/public/com/atlassian/amps/at lassian-amps-product-plugins/5.0.4/atlassian-amps-product-plugins-5.0.4.pom Downloaded: https://maven.atlassian.com/repository/public/com/atlassian/amps/atl assian-amps-product-plugins/5.0.4/atlassian-amps-product-plugins-5.0.4.pom (8 KB at 69.5 KB/sec) Downloading: https://maven.atlassian.com/repository/public/com/atlassian/maven/p lugins/maven-refapp-plugin/5.0.4/maven-refapp-plugin-5.0.4.jar Downloaded: https://maven.atlassian.com/repository/public/com/atlassian/maven/pl ugins/maven-refapp-plugin/5.0.4/maven-refapp-plugin-5.0.4.jar (60 KB at 412.1 KB /sec) Downloading: https://maven.atlassian.com/repository/public/com/atlassian/refapp/ atlassian-platform/2.23.2/atlassian-platform-2.23.2.pom Downloading: file://C:\Users\jbs\atlassian-plugin-sdk/repository/com/atlassian/r efapp/atlassian-platform/2.23.2/atlassian-platform-2.23.2.pom Downloading: http://repo.maven.apache.org/maven2/com/atlassian/refapp/atlassian- platform/2.23.2/atlassian-platform-2.23.2.pom [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project testId:artId:1.0 (C:\atlastutorial\artId\pom.xml) has 1 er ror [ERROR] Non-resolvable import POM: Could not find artifact com.atlassian.ref app:atlassian-platform:pom:2.23.2 in atlassian-public (https://maven.atlassian.c om/repository/public) @ line 70, column 25 -> [Help 2] [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/ProjectBuildin gException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableMo delException

1 vote
Robert Massaioli _Atlassian_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 19, 2014

Okay, I don't know what your problem is exactly but I know that you don't need a pom to get atlas-run-standalone to work. What I would recommend is following the atlassian-connect documentation because it will even give you the version of JIRA that maps to (nearly) the latest running OnDemand versions:

https://developer.atlassian.com/static/connect/docs/guides/getting-started.html#runjira

The important part there is:

atlas-run-standalone --product jira --version 6.4-OD-09-008 --bundled-plugins com.atlassian.bundles:json-schema-validator-atlassian-bundle:1.0.4,com.atlassian.webhooks:atlassian-webhooks-plugin:1.0.6,com.atlassian.upm:atlassian-universal-plugin-manager-plugin:2.17.14-D20140902T224549,com.atlassian.jwt:jwt-plugin:1.2.2,com.atlassian.plugins:atlassian-connect-plugin:1.1.13 --jvmargs -Datlassian.upm.on.demand=true

Which you can probably shorten to:

atlas-run-standalone --product jira --version 6.4-OD-09-008 --jvmargs -Datlassian.upm.on.demand=true

Ben Sheppard November 20, 2014

What exactly is all of this supposed to accomplish? I followed your shortened command, and got it to load correctly. I have a jira instance running on my local machine, but all I want to be able to do is to access my cloud Jira installation via the REST API. I've been following your instructions from https://answers.atlassian.com/questions/10413885/comments/10414422?src=email and it seems like I'm getting further and further away from what I'm trying to accomplish.

0 votes
John Chin
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 20, 2015

I've encounter this problem and I've managed to resolved it by adding some parameter to my settings.xml file via /.m2 directory. The parameter is this:

<pluginRepository>
    <id>atlassian-plugin-sdk</id>
    <url>file://${env.ATLAS_HOME}/repository</url>
     <releases>
        <enabled>true</enabled>
        <checksumPolicy>warn</checksumPolicy>
      </releases>
      <snapshots>
         <enabled>false</enabled>
      </snapshots>
 </pluginRepository>

Reference: https://developer.atlassian.com/docs/getting-started/set-up-the-atlassian-plugin-sdk-and-build-a-project/explore-the-installed-sdk-and-the-atlas-commands#ExploretheInstalledSDKandtheatlasCommands-Step2:(Optional)Configurea<proxy>intheMavensettings.xml

TAGS
AUG Leaders

Atlassian Community Events