Jira Software 11.0 and Jira Service Management 11.0 EAP 02 is now available

@RobertKlimkiewicz any update on my question? We’re not able to run Jira Software.

Hi @RobertKlimkiewicz, @bcinarli and whole Atlassian Stuff,

I was trying to use recent platform-public-api-8.0.0-m16.pom and guess what’s happened? Right, building process had failed with the next error:

... Could not collect dependencies for project ... 
Caused by: The following artifacts could not be resolved:
    ... com.atlassian.upm:licensing-api:pom:8.0.0-m006 (absent)
    ... com.atlassian.upm:upm-api:pom:8.0.0-m006 (absent)
    ... com.atlassian.security:atlassian-password-encoder:pom:7.0.0-m014 (absent)
    ... com.atlassian.security:atlassian-secure-random:pom:7.0.0-m014 (absent)
    ... com.atlassian.security:atlassian-secure-xml:pom:7.0.0-m014 (absent)
    ... com.atlassian.security:atlassian-secure-utils:pom:7.0.0-m014 (absent)
    ... com.atlassian.oauth:atlassian-oauth-api:pom:7.0.2 (absent)

I leave this without any hopes to get answered, but I really sure you guys must do something with that systematic problem.

There was an issue with the Jira Agile. Please see: https://jira.atlassian.com/browse/JRASERVER-78888
It is fixed yesterday. The next EAP will have the fix

@pch , seems like that issue was different.

Are you able to reproduce it?