Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Atlassian Connect Express does not de-register addon

martin March 5, 2015

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? 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

2 votes
Daniel Wester
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 6, 2015

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

martin March 8, 2015

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?

TAGS
AUG Leaders

Atlassian Community Events