Jean-Baptiste,
I would definitely avoid any major changes before the release (if all goes well, we could have a new ServiceMix release by the end of next week - yay!), but feel free to remove them after that. However, I don't think just removing the dependencies in itself will help a lot. We want to make it as easy as possible to manage the assembly building process and to add new features to ServiceMix as we move along and I think it will take more than just removing the dependencies. We'll probably have to do a bit of investigation into what is the best way for us, but the KAR/OBR/... support that's been added to Karaf should allow us find a suitable mix of solutions for what we're doing at the ServiceMix project. Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Fri, Feb 4, 2011 at 7:59 PM, Jean-Baptiste Onofré <[email protected]> wrote: > Hi all, > > Starting with Karaf features plugin 2.1.3, it's not more required to have > artifacts in the local repo before calling add-features-to-repo goal. > Now, the plugin is able to download the artifacts from maven repositories > and add to the local repo. > > In the NMR and Features assembly, we have a huge part of the POM only > dedicated to the dependencies. > > I propose (after the next NMR and Features releases) to cleanup the POM to > remove the dependencies set. > > WDYT ? > > Regards > JB >
