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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs