Hello,<br>   To ease the management of the packaging configuration I&#39;ve commited a new version of it : packaging-new (not yet plugged in the maven reactor, but usable).<br>   The goal of it is to reduce step by step the need of changes in those packaging files (.js).<br>

   This work is related to GTNPORTAL-24<br><br>   Packaging-new:<br>     * Versions are now collected from the gatein-parent pom (the properties), so no more need to update any .js file for our daily components. (dependencies versions still to be managed for the moment).<br>

     * .js files of JCR/Core/Kernel/WS are attached to those products and downloaded as maven dependencies, so the management of those files will be done in the EXOJCR project<br><br>   This packaging we&#39;ll be needed as soon as we use the new JCR/Core/Kernel/Ws tags that are beeing prepared for tomorrow by the JCR Team<br>

<br>    What&#39;s next (for Beta2):<br>    * Add some new packaging features to create standalone ear for customer applications (upcoming work).<br><br>    What&#39;s next (after Beta2):<br>    * Find a way to use pom.xml file instead of modules.js<br>

    * Have the exopackage turned into a maven plugin coded in Java, and integrated in GateIn for an easier management<br>   <br clear="all">Dimitri BAELI - eXo Platform SAS<br>