Atlas-run should fail if my plugin isn't loaded

Why? Because of this:

[INFO] amps:stop in 54s

Plus, add on all the time atlas-run takes from the time my plugin fails to the time jira is up and running and ready to be shutdown gracefully.

I am wasting several minutes every time something goes wrong.

If the plugin fails, then just fix the problem and use ‘atlas-package’ to repackage it. If you have quickreload set up, then it should reinstall the plugin immediately at runtime. You shouldn’t need to stop and start the full container.

1 Like

Wow, I was thinking that to “reload” something, it actually had to be “loaded” in the first place. LOL

Thanks so much!

1 Like

You can speed it up even more if you do auto-save / auto-package in your IDE. For front-end stuff, I use nodemon to start atlas-mvn package on changes

1 Like