Jira 10.1 EAP 01 and EAP 02 have been released!

RobertKlimkiewicz · September 6, 2024, 2:08pm

Hi, Developer Community! The second EAP for Jira Software 10.1 and Jira Service Management 10.1 is ready for testing.

Starting from Jira 10.1, we’ve moved the communication about Jira Software Data Center and Jira Service Management Data Center development releases to the Jira development releases page. With this transition, we aim to provide you with a single source of information about improvements and changes to our products.

You can download the EAPs from this page. If you’re using maven.atlassian.com, here is the version for both Jira Software and Jira Service Management:

10.1.0-m0001 for EAP 01
10.1.0-m0003 for EAP 02

If you have any comments, feel free to share them below them below.

Happy testing,
The Jira Data Center team

paul · September 6, 2024, 8:57pm

What is the username and password for the maven repository? It doesn’t work with my Atlassian one

Thanks
Paul

david · September 6, 2024, 9:27pm

You need a password for the maven repo? Since when?

paul · September 7, 2024, 12:37am

Don’t know. I clicked on the link and it asked for a username and password. I entered my Atlassian login and it just showed a 410 Gone error page

AndreasEbert · September 9, 2024, 6:27am

@paul @RobertKlimkiewicz see Atlassian maven.atlassian.com is now packages.atlassian.com.

RobertKlimkiewicz · September 10, 2024, 11:44am

Hi,
packages.atlassian.com should work fine and the page doesn’t ask to log it: https://packages.atlassian.com/ui/repos/tree/General/

Indeed, we migrated from maven to packages some time ago, but we keep using the name “maven” as it’s commonly known. We set up a redirect to avoid confusion

Best regards,
Robert from Jira Data Center team

AndreasEbert · September 11, 2024, 6:20am

@RobertKlimkiewicz, yes, it does:

RobertKlimkiewicz · September 11, 2024, 10:00pm

Hi Andreas,
I’m not sure what’s the reason to be honest. Maybe your token has expired and now maven is failing to get the dependencies?

Download the JSW 10.1.0-m0001 obr, this should accessible without any auth, and outside our network

richard.white · September 11, 2024, 10:04pm

@RobertKlimkiewicz

Just FYI - packages.atlassian.com also asks for auth for us here. I don’t think the issue is on Andreas’ side.

Your download for obr directly is accessible though. The actual repository index is still accessible ie: Index of maven-closedsource/ - just the artifactory UI that is password protected I guess?

adam.labus · September 19, 2024, 7:44pm

Hi Guys,

I don’t know why, but in versions 10.0.1 and 10.1.0-m0001 I got NCDFE, the same code works fine on version 10.0.0.

Caused by: com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: com/atlassian/plugin/web/model/WebFragmentBuilder
    	at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2085) [guava-32.1.3-jre.jar:?]
    	at com.google.common.cache.LocalCache.get(LocalCache.java:4019) [guava-32.1.3-jre.jar:?]
    	at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:4042) [guava-32.1.3-jre.jar:?]
    	at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:5024) [guava-32.1.3-jre.jar:?]
    	at com.google.common.cache.LocalCache$LocalLoadingCache.getUnchecked(LocalCache.java:5031) [guava-32.1.3-jre.jar:?]
    	at com.atlassian.jira.plugin.webfragment.ThreadLocalCachingSimpleLinkManager.getLinksForSection(ThreadLocalCachingSimpleLinkManager.java:166) [classes/:?]
    	at com.atlassian.jira.plugin.webfragment.ThreadLocalCachingSimpleLinkManager.getLinksForSection(ThreadLocalCachingSimpleLinkManager.java:153) [classes/:?]
    	at jdk.internal.reflect.GeneratedMethodAccessor634.invoke(Unknown Source) [?:?]
    	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [?:?]
    	at java.base/java.lang.reflect.Method.invoke(Method.java:569) [?:?]
    	at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26) [atlassian-plugins-core-8.0.17.jar:?]
    	at jdk.proxy3/jdk.proxy3.$Proxy364.getLinksForSection(Unknown Source) [?:?]
    	at jdk.internal.reflect.GeneratedMethodAccessor634.invoke(Unknown Source) [?:?]
    	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [?:?]

@mkemp @AndrzejKotas - can you confirm that something has changed in versions 10.0.1 and 10.1.0-m0001 compared to 10.0.0 for the WebFragmentBuilder class?

UPDATE: ahhhh, I actually see that the migration to P7 mentions the removal of this class, but it’s strange that in version 10.0.0 it was still available and disappeared only from version 10.0.1, which had a slight impact on our clients
https://bitbucket.org/atlassian/atlassian-plugins-webfragment/src/master/UPGRADE_700.md
It would be nice if the compiler informed about the lack of access to a given class instead of throwing NCDFE exceptions only when someone uses a given functionality in the application - please consider this option

Cheers
Adam

mkemp · September 20, 2024, 7:50am

The rule of thumb is anything that ends with -api and doesn’t have internal in the artifactId is fair game, while anything else might be internal. Apologies, we have yet to define API for everything so sometimes you may have to use a non -api module.

For Web Fragments, API is now well defined, so you should be able to use everything you need from:

<dependency>
    <groupId>com.atlassian.plugins</groupId>
    <artifactId>atlassian-plugins-webfragment-api</artifactId>
    <scope>provided</scope>
</dependency>

What could also happen is that there is a dependency on something else which has an incorrectly declared Maved dependency on <artifactId>atlassian-plugins-webfragment</artifactId> which would lead the compiler to believing the class is usable. If you spot this, please let us know and we’ll fix it.

We’re trying to wrangle the Maven dependencies to solve exactly that second problem.

adam.labus · September 20, 2024, 8:04am

Hi @mkemp

Thank you for the information

Ultimately, I used the suggested solution and switched to interface implementations. Now everything works with versions from 10.0.0 to currently 10.1.0-m0001.

Cheers
Adam

adam.labus · September 20, 2024, 11:52am

Hi Atlassian Team,

In the workflow preview (Issue View, EditWorkflowScheme.jspa), the AUI Dialog is probably closed incorrectly, causing the buttons to not be visible correctly.

Tested on version 10.1.0-m0001 and 10.1.0-m0003

d

Cheers
Adam

RobertKlimkiewicz · September 20, 2024, 2:33pm

Hello everybody!

Jira 10.1 EAP 02 have been released today. The maven is version 10.1.0-m0003. I’ve edited the name of this topic and it’s content accordingly to include the latest EAP details.

Happy testing!
Robert from Jira Data Center team