On 10/11/2011 10:04 AM, Thomas Mortagne wrote:
hi devs,
The idea is that in Maven in general you should never embed anything except for final distribution packages that are not supposed to be used as dependencies of other maven projects (installers, standalone packages, etc.). This will also allow us to properly setup dependencies in xar so that dependency is installed when installing a xar in Extension Manager without its pages being imported twice.
So I propose the following changes: * in xar plugin: ** stop embedding dependencies as default behavior
+1
** introduce an optional property for it.
+0
* in XE/XEM have two different xars: ** a normal one with just XE pages and proper dependencies setup ** a "standalone" one which embed all XE dependencies xar (basically the one we have now)
Not quite sure I like this. First, we're supposed to be moving documents out of xwiki-enterprise and into application modules inside the platform, so there shouldn't be any XE XAR at all, just a list of default dependencies to include in the standalone database. Second, if we do push forward the extension manager as the preferred way of installing XARs, then such a bundle XAR shouldn't be needed at all. For the standalone distribution the packager plugin could just install the XE shallow XAR + its dependencies, while for WAR installs users could just pull it using the extension manager. So, the big fat XAR shouldn't have any use either.
WDYT ?
Here is my +1
-- Sergiu Dumitriu http://purl.org/net/sergiu/