Hi @Wendy
Thanks for the update here.
I see a number of changes in the Confluence 8.7 beta that are not enumerated in the “Preparing for” page:
- When installing third-party apps, the system now logs a number of warnings about deprecated OSGi imports. See the thread I posted earlier this week. Can we get an official reaction from the dev team so we can understand what is going on? For example, when are these being removed? Is there an official list, or do we trust the list buried in the code that is shipping?
- When attempting to build against 8.7.0-beta1, a significant number of transitive dependencies were removed from the main
com.atlassian.confluence:confluence
package in Maven (compared to 8.6.0), which cause new errors when trying to build against those dependencies. Why were these removed? Many of these packages are still exported are they are not part of the deprecation list in #1 above. Apps can still manually include the dependency for these components in their own POMs (and then the app works successfully), but this change is unhelpful. Is there another dependency we can include in order to import the full list of whatever is available? Manually declaring the dependencies is suboptimal, because vendors now have to manually sync the component versions every time Confluence itself is upgraded, in order to ensure that our code still builds against the API. This process used to be automatic by just changing the Confluence version number, so this is a downgrade that introduces additional complexity.
For #2, the dependencies that were removed include: atlassian-mail, atlassian-plugins-webresource-common, atlassian-util-concurrent, xstream, and presumably many others.
Thanks!
Scott