Confluence 11.0 release EAP available now

Confluence Development
,
1

Hi everyone,

A Confluence 11.0 EAP milestone is now available. EAP releases provide a snapshot of our work in progress and give you an opportunity to test and fix your apps before the final release.

During the development of Confluence 11.0, we’ll release monthly milestones and betas. To find out what’s changed, head to Preparing for Confluence 11.0

Get the latest EAP

If you have any problems with an EAP release, please raise an issue to let us know. The earlier we know about problems, the more time we’ll have to fix them before the final release.

Enjoy!

The Atlassian Confluence team

We now announce Confluence Data Center releases and more in the Atlassian developer changelog. Subscribe to the changelog to receive the latest updates.

2 Likes
2

Hi @AleksandraWieczorek

Thank you for officially sharing it.

From my initial observations, it appears that some *Dao classes have been moved and are no longer available for us.

Looking at our code, we’re missing an equivalent to the getBlogPostByTitle(String spaceKey, String title) method from BlogPostDao.

Is there an alternative in the PageManager class (I haven’t found one) or should it be added to it?

Cheers

Adam

FYI @Kusal

2 Likes
3

Hi,

are there any Plattform major level upgrades?

Or other breaking changes?

Hard to believe that a major level version step from 10 to 11 does not bring any breaking changes.

The preparing page did not really contain any information about that.

Thanks

3 Likes
4

I’m genuinely surprised that a product with an announced end-of-life date is still doing major version releases.

I can only hope that the move from 10 → 11 is much smoother than the jump from 9 → 10 was, both in terms of development/testing (looking at you javax → Jakarta), as well as the ongoing burden of managing multiple builds/releases of our apps targeting each major.

For much of the lifetime of our apps we were able to have one build that worked across Confluence 6.x - 9.x. That ended with v10, and we now publish two version of every release (one for 6.x-9.x, and another for 10.x); and this was further complicated by the new process that requires every new version to go through an automated approval step which adds a minimum of 10-15 minutes to each version published.

If 11.x requires us to add a third build, we’ll have to seriously consider whether it’s worth continuing to offer DC versions given the dwindling expected sales.

5 Likes
5

Hey there!

I ran into two problems:

  1. Running lombok under JDK 23+ you need to add lombok as annotation processor: Maven :check_mark:

  2. Package com.atlassian.mail.queue is not present when importing com.atlassian.mail.queue.MailQueueItem; :cross_mark:

1 Like
6

Just my 2 cent…

Agree, if not totally necessary it should be in maintenance mode otherwise these platform upgrades (as these are more challenging) can lead to upgrade fatigue because “someone“ is migrating in x-months anyhow. I think every customers knows already how the deal with the regular jQuery finding :smiley:

If i’m not wrong, we had a CVE with a score of 10 on Confluence 8.x due to the underlying switch from WebWork to Struts. So these platform changes will not automatically increase security.