This build is centered around exposing Jira with its internal REST subsystem migrated to RESTv2. Currently, REST v2 affects Jira Software (JSW) DC exclusively. JSM is also part of the scope for RESTv2 and is currently undergoing migration. It will be included in future EAPs.
Hi @AndrzejKotas
I have a question. Is it normal that our Marketplace Addon without any Platform 7 changes works correctly in Jira 10?
What was the goal of this EAP?
It seems like com.atlassian.crowd.manager.directory.DirectoryManager
is not available with the Jira 10 EAP. com.atlassian.crowd.manager.directory is listed as exported package in the System Bundle and the same code works with the Confluence 9 EAP, so Iām assuming this is not intended.
This EAP was shipped with the capacity to still service the old REST subsystem. You should dive deep into the migration guide and migrate your Addon to new REST. That will be part of your Jira 10 / Platform 7 adaptation, and more platform components will change and will require further work. From our experience this is the most tricky part thatās why we focused to ship this milestone to you as soon as we could.
Your plugin might work, just as some of the bundled plugins shipped with this EAP work. But there are some that already use the v2 subsystem, including main Jira REST api and beans (serialising/deserialising Jiraās REST API beans with RESTv1 will fail in many places). The objective is to go off old Jersey and Jackson, both are our forks, so they need to go. Please refer to the linked guide and post here if you have questions.
I see you have your own system for local development so I understand if this isnāt pressing for you right now (of course with Platform 7 too), but if the issues you experienced werenāt the same as the thread and werenāt the same as any youāve previously reported on our issue trackers could you please create a new developer community thread and tag me? I would like to get our frontend development tooling in tip-top shape again.
Iām sorry I donāt have any immediate answers for you, weād need to spend some time digging deeper, it can be complex.
We will revisit the thread and update the example, but first our team is focusing on Platform 7 issues as they crop up and fixing other WRM Webpack Plugin bugs
Thank you for your clarification.
Iām already familiar with the migration guide and Iām aware of the changes to the REST API. Iāve already started migrating our plugin, but the latest EAP doesnāt guarantee that the changes Iāve made are complete.
Since the final version of Jira 10 is still up in the air, Iām unsure how well my current changes will work with older versions of Jira, nor am I certain which changes will be compatible with the final version of Jira 10.
When can we expect an EAP that is closer to the final version of Jira 10?
@JrgBrandsttt Thank you for raising the issue. It seems the EAP carried undocumented changes in Crowd aimed for Platform 7.
Iām taking this to the Platform and Crowd teams. Iāll confirm whether the effect youāre observing is coming to future Confluence EAP releases, or if it is a bug.
H2 will be removed from supported platforms as an embedded database. Weāre also removing the whole evaluation flow which used H2 during trial time.
If you choose to continue using H2 database in your development and testing cycle it may still work, depending you provide it, but we cannot guarantee it.
Does this mean that atlas-debug will be broken now?
Or H2 will be replaced with something else?
Is there an alternative jira-plugin-test-resources-xxx dumps for other database engines?
We tried installing our plugins with no changes on Jira 10 EAP 2. Unfortunately they didnāt activate. In the logs we can see the error:
ā¦
Caused by: java.lang.ClassNotFoundException: com.atlassian.jira.rest.v2.search.FilterBean not found by com.easesolutions.jira.plugins.testmanagement [253]
ā¦
Hi @lexek-92, H2 library will still be bundled by amps and nothing will really change. Please keep in mind that we donāt support H2 anymore and we may remove it in the future.
Hi! Yes, we have already removed this dependency.
We have also apparently mistakenly advised to migrate to FuncTestCase whereas we should migrate from it to com.atlassian.jira.functest.framework.BaseJiraFuncTest.
