AnsweredAssumed Answered

Extensibility modules still auto deploying

Question asked by tonyrivet on May 29, 2015
Latest reply on Aug 3, 2015 by ddraper
Hi,

I have some Share extensibility modules that depend on each other. Initially, I configured them to auto-deploy. Then I figured out that :
- there is no better way to order the module deployment than doing it manually on the module deployment page
- when the auto-deploy property is set to true, the modules redeploy each time the server is restarted and the manually set order is lost

I read <a href="http://stackoverflow.com/a/14954794">here</a> that the only way to manage extensibility modules deployment order is to set the auto-deploy property to false and to set the order manually.
That's quite a shame, but ok…

My problem is setting the auto-deploy to false seems to have no effect : my modules still deploy automatically each time I restart tomcat, and so I loose the deployment order…

I also changed the WebFramework configuration without any effect :

<config evaluator="string-compare" condition="WebFramework">
      <web-framework>
         <module-deployment>
            <!– Allow extension modules with <auto-deploy> set to true to be automatically deployed –>
            <mode>manual</mode>
            <enable-auto-deploy-modules>false</enable-auto-deploy-modules>
         </module-deployment>
      </web-framework>
</config>


Does someone know why the modules still auto deploy?
Is there any attribute persisted in database that I could reinitialize (I can't afford to wipe the database here)?

Thank you for your answers !

Tony

Outcomes