It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Is it a good practice to avoid Spring Scanners in Jira add-on..?
In some answers, it was told to remove the usage the Spring scanners from pom.xml to avoid errors.Is it necessary to use Spring Scanners in Jira add-on..?
If Spring scanners are necessary, Which version we should use either 1 or 2 ?
The default Jira command atlas-create-jira-plugin creates plugins with Spring scanners with version 1+ . Is it good to develop addon with Spring scanner version 1..?
Using spring scanner is not mandatory. But it is recommended because they create "transformerless" plugins. As per the doc:
"They load significantly faster than traditional P2 plugins that require runtime transformation. Local tests for example show plugins that took 5 seconds to load now load in under 2 seconds."
I'm sure using v1 is fine but I would use v2, if possible, because it is likely to have many improvements. I haven't checked the details though.
Hi @Jobin Kuruvilla [Go2Group] did you had a change to give v2 a try? I would like to initialize a plugin with v2 but it always stuck at some point and no luck with the readme in spring scanner repo of Atlassian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Jira Service Desk marketing team is working on a guide to help new Atlassian customers switch from email to JSD and we'd love to hear from you! Please share: - What made you realize that i...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.