EAP milestone 04 for Jira Server 8.0 has just arrived!

Jira Development Jira Data Center Announcements
, ,
1

…and is ready for action!

You can test further Lucene improvements, upgraded Apache Tomcat, and jQuery version 2.2.4, to name just a few breaking changes. You can also enjoy the new look and feel of the Scrum/Kanban boards and backlogs.

Make sure you read our Preparing for Jira 8.0 notes because the Apache Tomcat upgrade might require an action on your side.

You can download this EAP here. If you use the maven.atlassian.com site, get milestone 8.0.0-m0012.

More breaking changes?

The good news is, we are nearly done! You can still expect some changes related to the Java upgrade in the next EAP milestone, but that’s mostly it!

Got feedback?

Did you like the milestone or want to suggest an improvement? Leave us a comment on the developer community.

What’s the scope?

If you want to review the full set of changes for Jira 8.0, refer to the Jira 8.0 announcement.

Best,
The Jira team

2 Likes
3

Left a comment @developer community .

4

@mmichalak hi, I just did a test install of JIRA Software 8.0.0-m0012
and my plugin that works fine for JIRA 7 now gets NullPointerExceptions when accessing dependencies that are injected via setters.
Are there any breaking changes regarding dependency injection?

I get:

Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: 
No qualifying bean of type 
'com.atlassian.jira.config.properties.ApplicationProperties' 
available: expected at least 1 bean which qualifies as autowire candidate. 
Dependency annotations: 
{@com.atlassian.plugin.spring.scanner.annotation.imports.ComponentImport(value=)}

Ok there seems to be no way to get ApplicationProperties to work. I seem to no t need id anyway. But I had to change the way of Dependency Injection in all my RestEndpoints and WebWork actions.

This works in JIRA 8

public MyClassAction {
    private LoginUriProvider loginUriProvider,
    private MyService myService

    @Inject
    public MyClassAction(
        @ComponentImport LoginUriProvider loginUriProvider,
        MyService myService
      ) {
          this.loginUriProvider = loginUriProvider;
          this.myService = myService;
      }
      // ...
}

The old way that worked in JIRA 7 and below via setters in a BaseClass does not work anymore.

5

@mmichalak

JS Globals deprecation

Status: IMPLEMENTED (EAP m04)

JS globals are deprecated and due to be removed in one of the Jira 8.0.x releases. They are replaced with AMD modules.

Why not it 8.0.0? and can you share a list what exactly will be removed?

1 Like
6

I am also curious about that :slight_smile: ( JS Globals deprecation )

Will I still be able to do stuff like this with a plain JS file served as web resource?

var foo = AJS.$('#my-element');

AJS.$.ajax({
   url: restUrl + "/foo",
   type: "PUT", 
   // ...
  });

var table = new AJS.RestfulTable({ /* ... */ });

I also would like detailed docs. I tested my JS code with M04 and it still works, but I am really afraid that some further change by atlassian will break my JS code :-/

7

Hey hey!
Thanks for reaching out. What you’re describing (dependency injection) is related to platform changes. You can see the details in the Platform change log.

1 Like
8

Thanks for reaching out to us!
The team might decide to keep all global variables in Jira 8.0 and gradually remove them in 8.x, with proper notice period. Once we decide to remove a particular subset of globals in Jira 8.x version - we will provide detailed migration documentation, containing removed globals list and their AMD module names equivalents. Hope this helps!

1 Like