Re: [xwiki-devs] [VOTE] Move all rendering related components under the same maven parent and separate a little more

On Jan 8, 2009, at 12:39 PM, Thomas Mortagne wrote: > On Thu, Jan 8, 2009 at 11:27 AM, Thomas Mortagne > &lt;thomas.mortagne(a)xwiki.com&gt; wrote: >> Also WDYT of creating a xwiki-core-rendering-all maven project >> which >> would be used as entry point to depends on all rendering >> components. >> This way we could remove all the things which are listed in old >> xwik-core project and just depends on xwiki-core-rendering-all ? > > Even i'm not sure what is the clean way to do it with maven. That's basically the same question Asiri asked yesterday but at the level of platform/core. IMO there must be a good reason to have separate modules. If not we must have a single module. If we do it means the modules are not all compulsory and can be used independently. This means that it's the pom that uses them that need to declare a dep on them for its needs. One thing that might help is to follow the BOM pattern defined here (<scope>import</scope>): http://maven.apache.org/guides/introduction/introduction-to-dependency-mech… I just discovered this notion of import scope and haven't used it before. However it seems we'll still need to declare the deps, it's only the versions that can be shared. If we go the rendering-all solution then I'd like that this module be a ubjerjar module, i.e. it generates a single jar for all the modules it aggregates (using the assembly plugin) and so that dependent projects have only 1 dependency which is that uberjar. WDYT?