L.S.,
Looks like we have a consensus here - raised https://issues.apache.org/jira/browse/SM-2242 to keep track of this. For the command to populate the system directory for offline use, wouldn't it be better to add that to Karaf instead? Regards, Gert Vanthienen On Wed, Feb 19, 2014 at 8:03 PM, Cristiano Costantini <[email protected]> wrote: > +1 as Achim > > > 2014-02-19 19:57 GMT+01:00 Achim Nierbeck <[email protected]>: > >> +1 for one distro and this special command to do fillup the system dir. >> >> >> 2014-02-19 19:29 GMT+01:00 Jon Anstey <[email protected]>: >> >> > +1 >> > >> > Having one distro is going to make polishing/testing a lot easier too. I >> > also like Raul's idea of having a command to fully populate the system >> dir >> > (or other dir) at a user's discretion. >> > >> > >> > On Wed, Feb 19, 2014 at 2:40 PM, Jean-Baptiste Onofré <[email protected] >> > >wrote: >> > >> > > Hi guys, >> > > >> > > I don't see a lot of value to full assembly and minimal: >> > > >> > > - if an user wants minimal, just use Karaf ;) >> > > - if an user really want full, just install NMR/JBI, etc in your SMX. >> > > >> > > I would keep only default assembly which is ready to use and >> extensible. >> > > >> > > Regards >> > > JB >> > > >> > > >> > > On 02/19/2014 11:46 AM, Gert Vanthienen wrote: >> > > >> > >> L.S., >> > >> >> > >> >> > >> Just noticed Krzysztof's comment about the how and why of the >> > >> apache-servicemix-full assembly in JIRA and think it's worth having a >> > >> quick discussion about which of these assemblies we want to keep >> > >> around going forward. >> > >> >> > >> Right now, we have 3 variations of our assembly in ServiceMix 5: >> > >> - The default assembly has a setup that includes the base CXF, Camel >> > >> and ActiveMQ bits and preinstalls those as boot features >> > >> - The minimal assembly actually has none of these things preinstalled, >> > >> it's just a plain Karaf with the feature URLs (among a few other >> > >> things) preconfigured - not sure how much this one is used though >> > >> - The full assembly is identical to default assembly, but the /system >> > >> folder contains all bundles for all optional features. This makes it >> > >> easy for people to use ServiceMix on servers that have no direct >> > >> connection to the internet. This one is probably used a bit more (I >> > >> usually install this one myself), but we are struggling to keep it >> > >> below the maximum 350000000 bytes distribution size (which is already >> > >> an exception to the rule at the ASF) and as issue >> > >> https://issues.apache.org/jira/browse/SM-2241 is showing, it is prone >> > >> to be impacted by any kind of error in any of our dependencies' >> > >> features files. >> > >> >> > >> For ServiceMix 5 and other upcoming versions, which of these >> > >> assemblies do we want to keep around? >> > >> >> > >> >> > >> Regards, >> > >> >> > >> Gert Vanthienen >> > >> >> > >> >> > > -- >> > > Jean-Baptiste Onofré >> > > [email protected] >> > > http://blog.nanthrax.net >> > > Talend - http://www.talend.com >> > > >> > >> > >> > >> > -- >> > Cheers, >> > Jon >> > --------------- >> > Red Hat, Inc. >> > Email: [email protected] >> > Web: http://redhat.com >> > Twitter: jon_anstey >> > Blog: http://janstey.blogspot.com >> > Author of Camel in Action: http://manning.com/ibsen >> > >> >> >> >> -- >> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & >> Project Lead >> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> >> Commiter & Project Lead >> blog <http://notizblog.nierbeck.de/> >>
