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

My JIRA Projects will not start anymore

Florian Marquardt April 15, 2014

if I call atlas-run or atlas-debug in my project I get the following Build Error message:

[INFO] Internal error in the plugin manager executing goal 'com.atlassian.maven.plugins:maven-amps-plugin:5.0-m1:validate-test-manifest': Unable to load the mojo 'com.atlassian.maven.plugins:maven-amp
s-plugin:5.0-m1:validate-test-manifest' in the plugin 'com.atlassian.maven.plugins:maven-amps-plugin'. A required class is missing: Lorg/apache/maven/plugin/BuildPluginManager;
org.apache.maven.plugin.BuildPluginManager

If I'm using the '-e' switch I get the following cause in the stack trace

Caused by: java.lang.ClassNotFoundException: org.apache.maven.plugin.BuildPluginManager
        at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
        at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195)
        at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255)
        at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274)
        at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
        ... 40 more

I suppose, that the URLClassLoader has some problems with our enterprise proxy. But the proxy settings in my settings.xml are correct.

Also using the switch -DskipAllPrompts=true as mentioned in [AMPS-895] leads to the same behaviour.

However if I use 'atlas-run-standalone' on my project it starts a refapp instance?!?! But I have a JIRA-Plugin-project ...

So right now I am not able to work on my JIRA project :(

PS.: I'm using Atlas-Version 4.2.12

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Answer accepted
Boris Georgiev _Appfire_
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.
April 15, 2014

Just add the following to your <build><plugins> section of your pom:

&lt;plugin&gt;
				&lt;groupId&gt;com.atlassian.maven.plugins&lt;/groupId&gt;
				&lt;artifactId&gt;maven-amps-plugin&lt;/artifactId&gt;
				&lt;version&gt;${amps.version}&lt;/version&gt;
				&lt;extensions&gt;true&lt;/extensions&gt;
      		&lt;/plugin&gt;

Florian Marquardt April 15, 2014

That really worked, but its odd. As far as I remember I never changed this in the pom. But the project already worked in past.

Boris Georgiev _Appfire_
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.
April 15, 2014

It's not you, but AMPS bug. Google for this error and you'l find a lot of dicussions on that :)

TAGS
AUG Leaders

Atlassian Community Events