Hi Christian, You can do this right now in trunk with a karaf-assembly project.
I don't see how it really helps in a closed environment, nor do I understand how the proposed karaf-max will help. In my experience when you have a closed environment there's an approval process to get stuff into it. Despite Mike's first answer to me, I still don't understand how packaging 150 bundles into an assembly when you only need 100 will make that approval process easier. I'd also expect a closed environment to need to make most of the imported artifacts available to the build system which AFAICT neither Mike nor your proposal address. And, I still don't have any problem with adding such a mega-assembly. I don't think it will help anyone in a closed environment but it does seem like it might make all the possibilities easier to discover and play with. thanks david jencks On May 3, 2011, at 1:45 PM, Christian Schneider wrote: > Hi Mike, > > while this is sure possible it would be quite big. Especially if you also > would include other projects like camel or activemq. > > Instead I propose to add some commands to karaf to download dependencies to > the sytem dir. So the user could load karaf. Add the feature url he needs and > with some simple commands download them to the system dir. Then he can zip > the distro again and use it in the closed environment. > > I think that would be much more flexible. > > Christian > > > Am 03.05.2011 20:46, schrieb mikevan: >> For folks developing applications to deploy into Karaf on closed networks, it >> is not always feasable to be able to download all the optional packages for >> which we have optional console commands. I'm thinking web:, http:, obr:, >> and the like. >> >> I propse we create a new assembly for karaf that will include all of the >> optional bundles in the system directory for use in closed-networks. After >> talking about this topic on IRC it seems that many of us developing on >> closed networks have created work-arounds for this. Because there are so >> many work-arounds, perhaps its time to have a single Karaf-Max deployment >> that contains all of the optional bundles for karaf. >> >> If it helps, I can write it... :-) >> >> ----- >> Mike Van (aka karafman) >> Karaf Team (Contributor) >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/DISCUSS-Karaf-Max-assembly-tp2895460p2895460.html >> Sent from the Karaf - Dev mailing list archive at Nabble.com. >> > > -- > ---- > http://www.liquid-reality.de >