I understand that. What I meant is that you setup your distro in a place
with internet connection and then bring the distribution zip into the
closed environment.
Christian
Am 03.05.2011 22:56, schrieb Achim Nierbeck:
Hi Christian,
well the scenario Mike is talking of you are not able to download your
dependencies at all.
There are certain environments where you merely don't get the desired
downloads,
especially with maven.
so yes I can understand and support the idea of building an additional
distro including all
optional features.
regards, Achim
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
