[gatein-dev] GateIn packaging evolution : packaging-new to be used tomorrow

Hello, To ease the management of the packaging configuration I've commited a new version of it : packaging-new (not yet plugged in the maven reactor, but usable). The goal of it is to reduce step by step the need of changes in those packaging files (.js). This work is related to GTNPORTAL-24 Packaging-new: * 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). * .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 This packaging we'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 What's next (for Beta2): * Add some new packaging features to create standalone ear for customer applications (upcoming work). What's next (after Beta2): * Find a way to use pom.xml file instead of modules.js * Have the exopackage turned into a maven plugin coded in Java, and integrated in GateIn for an easier management Dimitri BAELI - eXo Platform SAS