Publising Modules within the Forge
Publishing modules is an activity for Developers, here you are a detailed explanation about how to publish your modules.
When first publishing your module to the Central Repository, please set its maturity status to Test, as discussed here.
You may want to first publish it as Test to ensure that your new module installs cleanly in a fresh Openbravo instance.
When testing the installation of your new module from your Openbravo instance, you must configure your Module Management Console window (Settings Tab) to search for new modules (All or only this particular one) in a "Test" maturity level. Note that since the default maturity level shown in the Module Management Console is "CS" (Confirmed Stable), your new "Test" module will not appear in the list, if you forget this step!!
If you are publishing a Commercial module, we recommend that you declare it as Available for Trial License.
Setting this flag means that users who opt for a free 30 Trial license of Openbravo Professional Edition will be able to install and try out your commercial module for 30 days.
When publishing one version of a module, if it is flagged then the module will be marked as Available for Trial License (so all versions of that module will be available).
Publishing a new version without the flag will not remove the flag from the module (to avoid current instances getting inconsistent).
It is possible for an Openbravo administrator to remove the Available for Trial License flag from a commercial module on the license control server, if it was set in error.