A Confluence 9.1 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.
As usual, we’ll be releasing weekly milestones and betas during the development of Confluence 9.1, so head to Preparing for Confluence 9.1 to find out what’s changed.
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.
Unfortunately, some artifacts are probably not available
atlas-package -U
[INFO] Project POM found
[INFO] Resolving plugin info, may take a while on the first run.
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Non-resolvable import POM: The following artifacts could not be resolved: com.atlassian.confluence:confluence-plugins-platform-pom:pom:9.1.0-m69 (absent): com.atlassian.confluence:confluence-plugins-platform-pom:pom:9.1.0-m69 was not found in https://packages.atlassian.com/maven-atlassian-external/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of atlassian-packages-external has elapsed or updates are forced @ line 191, column 25
[ERROR] 'dependencies.dependency.version' for com.atlassian.confluence.rest:confluence-rest-plugin:jar is missing. @ line 136, column 21
[ERROR] 'dependencies.dependency.version' for com.atlassian.confluence:confluence-rest-v2-api:jar is missing. @ line 141, column 21
[ERROR] 'dependencies.dependency.version' for com.atlassian.confluence.plugins:confluence-space-ia:jar is missing. @ line 151, column 21
[ERROR] 'dependencies.dependency.version' for com.atlassian.confluence:confluence:jar is missing. @ line 171, column 21
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.itlab.confluence.plugins:test-project:4.20.2-SNAPSHOT (/Users/r2d2/atlassian-workplace/test-project_9/pom.xml) has 5 errors
[ERROR] Non-resolvable import POM: The following artifacts could not be resolved: com.atlassian.confluence:confluence-plugins-platform-pom:pom:9.1.0-m69 (absent): com.atlassian.confluence:confluence-plugins-platform-pom:pom:9.1.0-m69 was not found in https://packages.atlassian.com/maven-atlassian-external/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of atlassian-packages-external has elapsed or updates are forced @ line 191, column 25 -> [Help 2]
[ERROR] 'dependencies.dependency.version' for com.atlassian.confluence.rest:confluence-rest-plugin:jar is missing. @ line 136, column 21
[ERROR] 'dependencies.dependency.version' for com.atlassian.confluence:confluence-rest-v2-api:jar is missing. @ line 141, column 21
[ERROR] 'dependencies.dependency.version' for com.atlassian.confluence.plugins:confluence-space-ia:jar is missing. @ line 151, column 21
[ERROR] 'dependencies.dependency.version' for com.atlassian.confluence:confluence:jar is missing. @ line 171, column 21
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
Confluence 9.1 rc1 gives me an error again. This worked in Confluence 9.0
org.glassfish.hk2.api.UnsatisfiedDependencyException:
There was no object available for injection at SystemInjecteeImpl
(requiredType=UserAccessor,parent=UsersEndpoint,qualifiers={},
position=1,optional=false,self=false,unqualified=null,1108564563)
But I am not trying to get UserAccessor but UserPreferencesAccessor like it worked with Confluence 9.0.
@Consumes({MediaType.APPLICATION_JSON})
@Produces({MediaType.APPLICATION_JSON})
@Path("/users/")
public class UsersEndpoint {
private final UserManager userManager;
private final UserPreferencesAccessor userPreferencesAccessor;
@Inject
public UsersEndpoint(UserManager userManager, UserPreferencesAccessor userPreferencesAccessor) {
this.userManager = userManager;
this.userPreferencesAccessor = userPreferencesAccessor;
}
....
What has changed since Confluence 9.0 to 9.1? What do I need to do?
thanks.
Also the pom.xml variable replacement does also not work anymore
Not sure where is best to put this, but when I run atlas-run-standalone -v 9.1.0-rc1 --product confluence, and then log into the Confluence instance, I am immediately taken to http://localhost:1990/confluence/undefined/index.action and greeted by a “Page Not Found” error.
I’m using SDK version 8.2.10 because SDK 9+ is broken by a missing dependency:
[ERROR] Failed to execute goal com.atlassian.maven.plugins:amps-maven-plugin:9.0.2:run-standalone (default-cli) on project standalone-pom: Unable to find/resolve artifact.: The following artifacts could not be resolved: com.atlassian.synchrony:synchrony-proxy:war:4.0.5 (absent): com.atlassian.synchrony:synchrony-proxy:war:4.0.5 was not found in https://repo1.maven.org/maven2/ ...
Maybe this is horrifying, but I don’t have a <platform.version> anywhere in my pom.xml. Should I? Where is that property used? My plugin is a very old codebase, so it’s possible that property was just never added.
Edit: actually, there’s no pom.xml involved here at all - I’m using atlas-run-standalone. I would expect there to be a “platform version” command line flag for that command, but I don’t see one (but maybe the docs are just outdated?).
Confluence 9.1 rc1 gives me an error again. This worked in Confluence 9.0
What has changed since Confluence 9.0 to 9.1? What do I need to do?
Should I? Where is that property used? My plugin is a very old codebase, so it’s possible that property was just never added.