Forums
Home Product Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Build error in atlas-run command when trying toload the hellowold plugin into Jira

Diogo Araujo
Diogo Araujo April 17, 2013

I am getting the following message error when trying to load the helloworld plugin into Jira:

[INFO] Scanning for projects...

[INFO] ------------------------------------------------------------------------

[INFO] Building helloworld

[INFO] task-segment: [com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:4.1.6:run]

[INFO] ------------------------------------------------------------------------

[INFO] Preparing amps-dispatcher:run

[INFO] ------------------------------------------------------------------------

[ERROR] BUILD ERROR

[INFO] ------------------------------------------------------------------------

[INFO] The plugin 'com.atlassian.maven.plugins:maven-amps-plugin' does not exist or no valid version could be found

[INFO] ------------------------------------------------------------------------

[INFO] Trace

org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'com.atlassian.maven.plugins:maven-amps-plugin' does not exist or no valid version could be found

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1546)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1786)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1274)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1238)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1031)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1009)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:627)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)

at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'com.atlassian.maven.plugins:maven-amps-plugin' does not exist or no valid version could be found

at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:229)

at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:91)

at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:172)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1517)

... 22 more

[INFO] ------------------------------------------------------------------------

[INFO] Total time: < 1 second

[INFO] Finished at: Thu Apr 18 11:15:54 BRT 2013

[INFO] Final Memory: 7M/18M

[INFO] ------------------------------------------------------------------------

Does anyone know how to fix this error?
Thanks.
Answer
Watch
Like Be the first to like this
888 views

3 answers

1 vote
Diogo Araujo
Diogo Araujo April 17, 2013

I am using Maven and the settings.xml is configured as shown below. I don't have a clue on what else to do.

Regardind localrepository:

<localRepository>c:/users/dearaujo/atlassian-plugin-sdk/repository/</localRepository>

----

Regarding m2-proxy repositories:

<repository>

<id>atlassian-public</id>

<url>https://m2proxy.atlassian.com/repository/public</url>

<snapshots>

<enabled>true</enabled>

<updatePolicy>never</updatePolicy>

<checksumPolicy>warn</checksumPolicy>

</snapshots>

<releases>

<enabled>true</enabled>

<checksumPolicy>warn</checksumPolicy>

</releases>

</repository>

<repository>

Reply
0 votes
Ramiro Pointis
Ramiro Pointis
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
April 17, 2013

Maybe it's a problem with the proxy. You could try the solution in this question:

https://answers.atlassian.com/questions/20079/plugin-sdk-does-not-use-http-proxy

Reply
0 votes
EddieW
EddieW
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
April 17, 2013

Are you using Maven, or the packaged atlas-mvn (or did youalter the path to the settings.xml?). I have seen similar errors when using my default maven install which does not include the Atlassian M2-Proxy repositories. YOU would see download warnings above the snippet you shared if this is the case.

View More Comments
Diogo Araujo
Diogo Araujo April 17, 2013

I am using Maven and the settings.xml is configured as shown below. I don't have a clue on what else to do.

Regardind localrepository:

<localRepository>c:/users/dearaujo/atlassian-plugin-sdk/repository/</localRepository>

----

Regarding m2-proxy repositories:

<repository>

<id>atlassian-public</id>

<url>https://m2proxy.atlassian.com/repository/public</url>

<snapshots>

<enabled>true</enabled>

<updatePolicy>never</updatePolicy>

<checksumPolicy>warn</checksumPolicy>

</snapshots>

<releases>

<enabled>true</enabled>

<checksumPolicy>warn</checksumPolicy>

</releases>

</repository>

<repository>

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Copyright © 2025 Atlassian
    Privacy Policy Terms Security
    Welcome illustration

    Welcome to the new Atlassian Community

    Online forums and learning are now in one easy-to-use experience.

    By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.