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
Community moderators have prevented the ability to post new answers.
Just add the following to your <build><plugins> section of your pom:
<plugin> <groupId>com.atlassian.maven.plugins</groupId> <artifactId>maven-amps-plugin</artifactId> <version>${amps.version}</version> <extensions>true</extensions> </plugin>
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's not you, but AMPS bug. Google for this error and you'l find a lot of dicussions on that :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.