Platform 7 upgrade in progress: Learn about the first highlights and changes

Announcements
, , , , ,
83

The versions in that table are meant to show the first version in which the changes are available in case you want to get access to them earlier. At this point, the latest Platform release should have all of them, so I expect products to ship with these changes as well.

As to what version the products will be releasing with… it’s hard to say, you’re probably better off asking in their respective threads. However, based on my knowledge they’re still in the process of adopting all of the changes, and we’re still releasing some bug fix updates on our end, so I don’t think we can quite designate a final Platform version yet.

1 Like
84

Gotcha, thank you for the clarification @TomRijnbeek !

85

Have you tried using Java Spring configuration? Here is a simple config from the RESTv2 helloworld.

86

Have you found a workaround for this since your post? I’m running into the same issue - REST module won’t enable on Confluence 8.7 or 8.8. All other versions appear fine.

Like you said, we’ll probably just have to wait till 9.0 release when the rest-migration module is presumably no longer required? I have an inkling of reading that somewhere, but finding that confirmation buried in some CDAC thread hasn’t borne fruit this afternoon.

87

We have opted to wait for the 9.0.0 release assuming that the rest-migration tag will no longer be necessary.

Off the top of my head, the only confirmation I am explicitly aware of that the tag will no longer be required is a comment in the source code indicating that a check involving the rest-migration tag will be removed in Platform 7.

It would be great to have a confirmation on this from an official channel.

3 Likes
88

Hi, starting from Platform 7.0, indeed the rest-migration tag is not necessary. REST v2 is used by default. The check associated with the rest-migration tag will be completely removed in the next minor version.

2 Likes
89

I’m working on updating the crowd-embedded packages to version 6.0.0-EAP01 (ref , and I’m encountering an issue I where I need some guidance.
When I previously tried installing with crowd 6.0.0-rc2 I got a similar issue also with net.sh.echache. I was then unable to find any reference to the package net.sf.ehcache:ehcache-parent browsing in https://packages.atlassian.com/mvn/maven-atlassian-external/.
Error output installing crowd-core:6.0.0-rc2:

Failed to collect dependencies at com.atlassian.crowd:embedded-crowd-core:jar:6.0.0-rc2 -> com.atlassian.crowd:crowd-core:jar:6.0.0-rc2 -> net.sf.ehcache:ehcache:jar:2.10.10-atlassian-2: Failed to read artifact descriptor for net.sf.ehcache:ehcache:jar:2.10.10-atlassian-2: The following artifacts could not be resolved: net.sf.ehcache:ehcache-parent:pom:3.1

When running mvn install it fails installing net.sf.ehcache (see below). I cannot seem to find net.sf.ehcache/2.10.10.20.11 anywhere in maven-atlassian-external when browsing manually either, but after a while I discovered them in maven central: https://mvnrepository.com/artifact/net.sf.ehcache/ehcache?repo=terracotta.
Error output with crowd-core:6.0.0-EAP01:

Could not resolve dependencies for project ...: The following artifacts could not be resolved: net.sf.ehcache:ehcache:jar:2.10.10.20.11 (absent): Could not find artifact net.sf.ehcache:ehcache:jar:2.10.10.20.11

Any advice on how to proceed would be appreciated. I see that the link to the package I found n maven central is actually broken: https://repo.terracotta.org/maven2/net/sf/ehcache/ehcache/2.10.10.20.11

Edit#1: I’m trying a workaround by manually downloading the jar and pom files which are available on central and manually installing them into my local .m2 and running an offline install

Edit#2: Deeper down the rabbit hole I’ve now manually installed ehcache and ehcache-root using mvn install:install-file. The remaining snag now is ehcache-root with a reference to ehcache-parent version 3.2, which apparently doesn’t exist online, but only points to a 404. I really wonder what’s the meaning of this. Does Atlassian have an internal fork with this package that’s offline?

Edit#3: Following up this one. I was able to fix the install of crowd-core by overriding the strange ehcache version in dependencyManagement, selecting a version that’s available on maven central:

<dependencyManagement>
      <dependency>
        <groupId>net.sf.ehcache</groupId>
        <artifactId>ehcache</artifactId>
        <version>2.10.9.2</version>
      </dependency>
</dependencyManagement>
90

Hi @MarekTokarski

OSGi exports : we have added com.[SOME_PROJECT_NAME].api in our pom.xml file. Do
we need to add anything specific ?

92

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