# Confluence 10.0 release is available now

**URL:** <https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350>\
**Category:** Confluence Data Center Announcements\
**Tags:** announcement, confluence-data-center, data-center\
**Created:** [August 5, 2025, 4:12pm UTC](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350 "2025-08-05T16:12:00Z")\
**Posts on this page:** 10\
**Page:** 2

<div class="post-metadata">

**Author:** ![metin](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/metin/32/54607_2.png) [@metin](https://community.developer.atlassian.com/u/metin)\
**Post date:** [August 11, 2025, 12:10pm UTC](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350/21 "2025-08-11T12:10:02Z")

</div>

We have found an incompatibility causing our app to cease to function.

We haven’t discovered this issue before, because it does or does not appear depending on the jar names, which were slightly different in our beta test environment. We assume that the jar names change the order in which the jars are loaded.

The issue causes the email protocol providers from our app not to be used although they are loaded. It may be an issue that is caused the Eclipse Angus mail library used in Confluence 10.

We’ve filed a ticket under ECOHELP-79631, but also wanted to make @Kusal and other partners aware of it.

The funny thing is, if we rename the _org.eclipse.angus\_angus-mail-2.0.4.jar_ to com.sun.mail…., it works again (but that does not feel like a reliable solution).

---

<div class="post-metadata">

**Author:** ![metin](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/metin/32/54607_2.png) [@metin](https://community.developer.atlassian.com/u/metin)\
**Post date:** [August 13, 2025, 12:47pm UTC](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350/22 "2025-08-13T12:47:28Z")

</div>

We’ve been able to track down the issue to a bug in the jakarta.mail-api library. The bug has already been fixed, and we are now awaiting the fix release, so Atlassian will _hopefully_ include it in their next Confluence 10 release.

---

<div class="post-metadata">

**Author:** ![metin](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/metin/32/54607_2.png) [@metin](https://community.developer.atlassian.com/u/metin)\
**Post date:** [August 13, 2025, 1:09pm UTC](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350/23 "2025-08-13T13:09:58Z")

</div>

Not sure what exactly is missing. Your approach is different from ours a few ways. Here’s what we do, perhaps it helps:

We have this script _setup-app-signing.sh_

```bash
#!/bin/bash

# Set up the Atlassian trust store for app signing

if ["$#" -ne 1]; then
    SCRIPT=`basename "$0"`
    echo "Usage: $SCRIPT 'path/to/certs/*'"
    exit 1
fi

CERTFILES=$1	

# Create necessary directories if they do not exist
mkdir -p upmconfig/truststore

# Create config file
cat >upmconfig/upm.properties <<EOD
atlassian.upm.signature.check.disabled=true
atlassian.upm.signature.check.upload.disabled=true
atlassian.upm.signature.check.marketplace.disabled=true
EOD

# Copy the certs
for CERTFILE in $CERTFILES; do
    cp $CERTFILE upmconfig/truststore/
done

```

Provided the Atlassian zip file has been extracted to certs/atlassian (not part of the script, but could become), then we

`setup-app-signing.sh 'certs/atlassian/*'`

---

<div class="post-metadata">

**Author:** ![aragot](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/aragot/32/36656_2.png) [@aragot](https://community.developer.atlassian.com/u/aragot)\
**Post date:** [August 14, 2025, 7:40am UTC](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350/24 "2025-08-14T07:40:22Z")

</div>

Hi Metin, thank you for your script! I’ve done the same. With `atlassian.upm.signature.check.disabled=true`, you are disabling app signing. And given how difficult it is to make it work, I assume most customers will do that.

---

<div class="post-metadata">

**Author:** ![cheinig](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/cheinig/32/55858_2.png) [@cheinig](https://community.developer.atlassian.com/u/cheinig)\
**Post date:** [August 25, 2025, 12:30pm UTC](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350/25 "2025-08-25T12:30:19Z")

</div>

@Kusal At least in Confluence 10.0.2, the `SpaceManager` has no Method `removeSpace` anymore.

There has been no mention of this in the “Preparing for …” page, and we need this method.

As far as I remember, the `SpaceService` methods respects the permissions of the current user, which we don’t want in our use cases.

Any suggestions? I don’t think we should use the Reflection API to get the method from `SpaceManagerInternal` / `DefaultSpaceManager…`

---

<div class="post-metadata">

**Author:** ![Kusal](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/kusal/32/46420_2.png) [@Kusal](https://community.developer.atlassian.com/u/Kusal)\
**Post date:** [September 22, 2025, 2:45am UTC](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350/26 "2025-09-22T02:45:57Z")

</div>

> [@cheinig](#):
>
> As far as I remember, the `SpaceService` methods respects the permissions of the current user, which we don’t want in our use cases.

If you wrap the `SpaceService` call in `com.atlassian.confluence.security.PermissionManager#withExemption`, it should run as an administrator.

---

<div class="post-metadata">

**Author:** ![JackNolddor](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/jacknolddor/32/50297_2.png) [@JackNolddor](https://community.developer.atlassian.com/u/JackNolddor)\
**Post date:** [October 1, 2025, 11:01am UTC](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350/27 "2025-10-01T11:01:17Z")

</div>

Seems like this piece of code is not working anymore on Confluence 10.x

```auto
public List<User> getActiveUsers()
{
    List<User> users = new ArrayList<>();

    PropertyRestriction<Boolean> isActiveRestriction = Restriction.on(UserTermKeys.ACTIVE).exactlyMatching(Boolean.TRUE);
    EntityQuery<User> userQuery = QueryBuilder.queryFor(User.class, EntityDescriptor.user())
            .with(isActiveRestriction)
            .returningAtMost(EntityQuery.ALL_RESULTS);

    crowdService.search(userQuery).forEach(users::add);

    return users;
}

```

What’s the correct way of creating that `userQuery` now as in Confluence 10.x plugins have no acccess to `QueryBuilder.class`

Any ideas @Kusal / @jponting ?

---

<div class="post-metadata">

**Author:** ![scott.dudley](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/scott.dudley/32/53884_2.png) [@scott.dudley](https://community.developer.atlassian.com/u/scott.dudley)\
**Post date:** [October 2, 2025, 3:23pm UTC](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350/28 "2025-10-02T15:23:16Z")

</div>

@JackNolddor The QueryBuilder class is working for us, so maybe it’s an import issue? I believe you need to include this in your POM:

```auto
        <dependency>
            <groupId>com.atlassian.crowd</groupId>
            <artifactId>crowd-api</artifactId>
            <scope>provided</scope>
        </dependency>

```

---

<div class="post-metadata">

**Author:** ![JackNolddor](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/jacknolddor/32/50297_2.png) [@JackNolddor](https://community.developer.atlassian.com/u/JackNolddor)\
**Post date:** [October 2, 2025, 4:09pm UTC](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350/29 "2025-10-02T16:09:19Z")

</div>

Hey! It was not needed on Confluence 9.x so indeed adding this as provided dependency solved the compilation issue. You rock!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/atlassiandeveloper/original/3X/7/8/78672baa5ba80cd9164376457051d0eec038b082.png) [@system](https://community.developer.atlassian.com/u/system)\
**Post date:** [November 1, 2025, 4:09pm UTC](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350/30 "2025-11-01T16:09:40Z")

</div>

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

[Previous page](https://community.developer.atlassian.com/t/confluence-10-0-release-is-available-now/94350.md?page=1)