When a product is started on a busy port, this will now cause the startup to fail with an error message rather than selecting a random port (see [AMPS-1462] - Ecosystem Jira for more)
Maven upgrade to 3.5.4
AMPS Maven Plugins and Product Plugins now follow Maven naming conventions (See [ATLASSDK-147] - Ecosystem Jira for details)
Full details will be found in the Release Notes (available later this week)
Important
AMPS 8.0.0 is not compatible with the Atlassian Plugin SDK version 6.x and earlier. If you’d like to use AMPS 8.0.0 with the Atlassian Plugin SDK, please wait for the Atlassian Plugin SDK version 8.0.0 release coming soon. Announcements will be posted in the Developer Community Forums.
We got Atlassian Plugin SDK 8 this morning via our package manager, we tried updating to AMPS 8 too but this broke all of our maven builds with the following output:
It seems a bit odd for the SDK to be complaining about non-Atlassian plugins? I could understand if the error was complaining about specific versions, but we should still be able to use standard maven artifacts right?
We might have jumped the gun, perhaps the above is addressed in the upcoming release notes.
@abhayani are there any release notes for this new SDK? Our builds are broken with AMPS 8/Plugin SDK 8, see my previous comment for the error we are getting.
I’m having issue with integration tests after upgrade.
Before the update I was running specific test groups with command like atlas-integration-test -DtestGroups=jira-current and it was running smoothly.
After the update and manually fixing atlas-integration-test script I now see the following output:
Executing: /usr/local/Cellar/atlassian-plugin-sdk/6.2.14/libexec/apache-maven-3.5.4/bin/mvn com.atlassian.maven.plugins:amps-maven-plugin:8.0.0:integration-test -gs /usr/local/Cellar/atlassian-plugin-sdk/6.2.14/libexec/apache-maven-3.5.4/conf/settings.xml -DtestGroups=jira-current
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
[INFO] Scanning for projects...
[INFO]
[INFO] --------------------< ru.mail.jira.plugins:groovy >---------------------
[INFO] Building MyGroovy 1.17.9
[INFO] --------------------------[ atlassian-plugin ]--------------------------
[INFO]
[INFO] --- amps-maven-plugin:8.0.0:integration-test (default-cli) @ groovy ---
[INFO] No integration tests found
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.594 s
[INFO] Finished at: 2019-02-15T11:44:54+03:00
[INFO] ------------------------------------------------------------------------
Maven repo doesn’t have the maven-jira-plugin:8.0.0
Unresolveable build extension: Plugin com.atlassian.maven.plugins:maven-jira-plugin:8.0.0 or one of its dependencies could not be resolved: Could not find artifact com.atlassian.maven.plugins:maven-jira-plugin:jar:8.0.0 in atlassian-public (https://maven.atlassian.com/repository/public)
Hi,
That ticket seems to be about maven command naming.
We’re having issue with tests not being found after workaround, which seems to be a different issue.