Confluence 8.8 is available now

It works, we use it every day. You’ll need to upgrade the version of the AMPS plugin to develop on newer versions of the products. The SDK commands will use the version of AMPS and the products in the pom.xml if specified.

You can see the release notes of AMPS here

We have spent time on getting Developer toolbox, Quickreload, Achoo DB console, Plugin viewer, Plugin data editor, and AMPS to keep them working on newer versions because we use them too.

If you see room for improvement or a bug, make a ticket on their respective public trackers. We also welcome contributions, most of them are in public repos.

1 Like

Hi @mkemp

You won’t believe it, but I tried to increase the AMPS to 8.13 and it didn’t help either, I assume that the problem is what was confirmed here

Cheers
Adam

1 Like

Apologies, I read your comment believing you were having troubles with the SDK being able to start Confluence and install the plugin - this is common to run into with using SDK commands as we took a long time to update its default version of AMPS. In this case it seems you actually just had issues with Confluence enabling the plugin.

Hello all,
I can understand the move of Atlassian to stop providing third-party libraries.
What I don’t understand is the strategy on Woodstox specifically.
Woodstox is delivered in Confluence in this file: /webapp/WEB-INF/lib/com.fasterxml.woodstox_woodstox-core-6.4.0.jar. It declares /META-INF/services/javax.xml.stream.XMLInputFactory, basically to say “anyone needing an XMLInputFactory instance will use my implementation”.
My Plugin (OSLC Connect for Confluence) uses Apache Jena which needs to obtain XMLInputFactory instances. The trick was to use:

<Import-Package>com.ctc.wstx.stax;resolution:="optional"</Import-Package>

This is more or less what is tracked for Jira in https://jira.atlassian.com/browse/JRASERVER-26214.
So far, so good.
But then Confluence 8.8 does no longer provides access to Woodstox implementation.
The result is my plug-in to be forced to use Woodstox but not having access to it, so forced to re-bundle Woodtox in my JAR file.
I don’t get that. As a platform, either provide this library or do not force me using it. Somewhere between the two is wrong.
Any hint?

3 Likes

Hi,

As of 8.8.0, I can no longer use LocalNotificationService, I now get this error.

java.lang.NoClassDefFoundError: com/atlassian/mywork/service/LocalNotificationService

What has happened? How do we send In-App notifications now. This has always been a nightmare to get working and now it is fully broken.

Atlassian, please supply instructions on how we can use this class, or what is the preferred way to use the Confluence Notifications.

All,
Based on the document provided for preparing for 8.8.0. It said " no runtime changes affecting the availabilities of these libraries and binary compatibility will be maintained". But when I try to deploy the code which was running on 8.7.1 on 8.8.0. It doesn’t seem to work. Asking for grey api libraries. (https://developer.atlassian.com/server/confluence/get-your-apps-ready-for-gray-api-removal/) Has anyone faced this problem, does anyone have a fix for this.

When the LocalNotificationService usage is figured out for 8.8+ it would be nice to have this doc updated: https://developer.atlassian.com/server/confluence/posting-notifications-in-confluence/

I thought that I had workbox notifications working in 8.8 but now I’m not so sure. I’m going to retest it. I am buried in other compat tasks but when I get back to this I’ll try to post something here if I really have gotten it working and can figure out my recipe.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.