How can I reduce the time for running my own plugin for Jira, using the "atlas-run" command?

[Daniela Mateescu]

Hello,

I have started to develop a plugin for Jira and now my problem is that running the application from command-line using the "atlas-run" command it takes to long . I know that, once I have started the application throw atlas-run I can reload the application every time I make a change throw the jira interface, accesing /jira/plugins/servlet/fastdev. But I want also that first time run of the application by much faster.

Thank you, in advance for your answers.

[Viðar Svansson · Accepted solution]

We have found the atlas-run/debug to run really slow on our Windows machines and the solution was to simply develop on Linux. The startup time is around 30 sec on Linux and usually couple of minutes on Windows. Not sure what causes this. Perhaps virus scanners.

[MB]

Confirmed. I switched from Windows 7 to Ubuntu 12.04 and reduced the start time from 4-5 minutes to a minute and a half.

[Mike at Black Pearl]

aftere you have your instance (jira/confluence) running with atlas-run, open another command window and use

atlas-package. This will regenerate the target/<plugin>.jar file. You can then manually re-install the plugin in the Administration->add-ons menu

I do this all the time and it is a lot faster than running atlas-run .. and BTW FASTDEV has NEVER WORKED!

(sorry for the yelling).

[BenW]

Fastdev is a great trick for speeding up dev time once the app is started. But as you said, starting up AMPS is still very slow.

I blame incredibly slow disk IO for my slow Windows development box. The slowest part of the process, in my opinion, is either starting up AMPS or cleaning my target directory.

This can be a dangerous solution but I'd recommend holding off on "atlas-clean" (or "mvn clean") as much as possible. This will make atlas-run start up much faster as AMPS will re-use your existing product installation in your target directory (so that Windows won't have to re-copy all the files every time you run "atlas-run"). And you won't have to wait forever for atlas-clean to complete either; I found that Windows takes forever to delete the target directory.

I say this can be a "dangerous solution" because without cleaning your target directory you will leave behind files from previous executions. So if you are removing or renaming a bunch of files, be sure to not skip atlas-clean.