In the documentation for ACE it seems like the plugin should be de-registered from the Confluence instance when shutting down the node server. This does not work for me.
I usually like to run the nodemon server which works brilliantly when updating JS files, but when I did some changes in the atlassian-connect.json I noticed that nothing happened so I tried to shut down the server and restarting it. Since nothing happened I went to Confluence admin and saw that the addon was still registered.
I solved the issue by manually de-registering the addon and then starting my node server again. It's a bit cumbersome, so my question is if this is by design or am I doing something wrong?
Community moderators have prevented the ability to post new answers.
So 2 part answer.
Part 1. I suspect that there is a bug/incorrect feature description about the de-registereing the add-on (I wouldn't think it would have time to do that).
Part 2. ACE had/has a bug in it in regards to the atlassian-connect.json in development mode. It would keep serving the initial version. 1.0.3 should fix that though
Thanks Daniel! I think I am running version 1.0.1 currently. Although I cannot find any instructions on how to upgrade ACE. You wouldn't happen to know how to do it? Is it simply a matter of changing the version number in the package.json file?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.