Can't run bitbucket server with atlas-run after upgrading to sdk 6.2.6

[Alexander Kitaev]

On Debian linux, I'm getting the following error:

[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:6.2.4:run (default-cli) on project stash-svn-importer: Unable to execute mojo: Could not build the MavenProject for com.atlassian.bitbucket.server:bitbucket-parent:pom:4.6.0: Error resolving project artifact: Failure to find com.atlassian.bitbucket.server:bitbucket-parent:pom:4.6.0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced for project com.atlassian.bitbucket.server:bitbucket-parent:pom:4.6.0 -> [Help 1]

[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[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 read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

I even tried to disable maven central repository in the pom.xml, but it didn't help.

[Alexander Kitaev]

I've partially resolved this issue by redirecting all request to central maven repository to Atlassian public maven repository in ~/.m2/settings.xml:

<mirrors>

<mirror>
 <id>central-proxy</id>
 <name>Local proxy of central repo</name>
 <url>https://maven.atlassian.com/repository/public</url>
 <mirrorOf>central</mirrorOf>
 </mirror>
 </mirrors>

after that atlas-run start working (though I do not believe that should be a standard way to make atlas-run work).

The new problem is that now atlas-run detects latest version of Bitbucket Server automatically and runs it, despite another version might be set in the add-on pom.xml. That means that there is no way to use atlas-run to run other than the latest version of Bitbucket Server (e.g. to test add-on with a particular version).

Looks like something is broken.

[Josh Wheeler]

I was able to spin up an instance of 4.5.0. You could just work off of that for now.

[Gabor]

Thanks, Alexander, this workaround helped.

[Alexander Kitaev]

Yes, I've worked around that by adding <mirror> for the maven central repository. The other problem with new SDK version is that atlas-run always runs the latest version of Bitbucket Server (4.6.0 at the moment).

Thanks for reply!

[Josh Wheeler]

It looks like, for some reason, the build process is trying to find the parent pom file on apache's site instead of maven's site (see here). I don't have a solution for you yet though...