atlas-run problem after update to SDK 4.2.18

[Frédéric Tardieu]

Hi all,

After updating Atlassian SDK to this version:

ATLAS Version:    4.2.18
ATLAS Home:       C:\Users\Fred\atlassian-plugin-sdk
ATLAS Scripts:    C:\Users\Fred\atlassian-plugin-sdk\bin
ATLAS Maven Home: C:\Users\Fred\atlassian-plugin-sdk\apache-maven
--------
Executing: "C:\Users\Fred\atlassian-plugin-sdk\apache-maven\bin\mvn.bat" --version -gs C:\Users\Fred\atlassian-plugin-sdk\apache-maven/conf/settings.xml
Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100)
Java version: 1.6.0_32
Java home: C:\Program Files\Java\jdk1.6.0_32\jre
Default locale: fr_FR, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"

I get an error building my JIRA plugin with atlas-run:

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[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-amps-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
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 30 seconds
[INFO] Finished at: Fri Mar 28 10:49:45 CET 2014
[INFO] Final Memory: 119M/379M
[INFO] ------------------------------------------------------------------------

Running atlas-clean before atlas-run does not change anything...

Does anyone have an idea about the cause of this problem?

Thank you and best regards,

Fred

[RambanamP · Accepted solution]

add this in your pom.xml

<plugin>
        <groupId>com.atlassian.maven.plugins</groupId>
        <artifactId>maven-amps-plugin</artifactId>
        <version>${amps.version}</version>
        <extensions>true</extensions>
    </plugin>

same question here

https://answers.atlassian.com/questions/277302/a-required-class-is-missing-lorg-apache-maven-plugin-buildpluginmanager?page=2#277824

[Lasse Christiansen]

Thanks for this, it works. But, why is this suddenly needed in the pom.xml file? And what does it do?

[Adrien Ragot 2]

This snippet tells Maven which version of maven-amps-plugin it should use. We need to specify it because the default version is the latest available, and the latest available isn't a stable release.

"AMPS" or maven-amps-plugin is the name of the Maven plugin made by Atlassian, that the SDK uses. What we saw in Frederic's logs is that Maven used maven-amps-plugin:5.0-m1 by default. It does that because it takes the latest available version.

The thing is, there's a developer working on maven-amps-plugin somewhere in Atlassian. As part of their work, they publish milestones for their colleagues to test. This is the event that made your setup fail: Obviously those milestones are work-in-progress and don't work for us. The problem is, when Maven takes the latest version, it takes this unfinished version, which is not what we want.

So we need to "pin" Maven to a specific stable version of AMPS.

[Sachin Dhamale]

hi rambanam;

After adding u mention code in pom file i get this error

[WARNING] [talledLocalContainer] org.codehaus.cargo.container.ContainerException: Port number 8009 (defined with the property cargo.tomcat.ajp.port) is in use. Please free it on th
e system or set it to a different port in the container configuration.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to execute mojo

can u tell me what is goes wrong please

[Adrien Ragot 2]

This is just because you still have an old build running in the background. Sometimes it happens, you believe you've stopped Maven, but the product is still running in the background.

• If you use a Mac or Linux, run "ps -fA |grep java", find the process that takes the port 8009 and kill it.
• If you use Windows, don't use Windows.

Best regards,

Adrien

[Sachin Dhamale]

hi Adrien

actually the port number is changing every time whenever i run atlas-run command

means its not constant port number (8009) it gives me different port number every time

[Adrien Ragot 2]

Bonjour Frédéric ;)

Do you have maven-amps-plugin or maven-jira-plugin in your pom.xml? Do they have the version, like Rambanam suggested? If so, try running the right maven goal:

• mvn amps:run (if you have maven-amps-plugin)
• mvn jira:run (if you have maven-jira-plugin)

Cheers,

Adrien

[Frédéric Tardieu]

Hi Rambanam, Salut Adrien ;-)

That was it, I was missing the version statement in maven.plugins section in pom.xml,

Thank you guys, everything fine now!

Cheers,

Fred