Hi Mike,
It could be interested. AFAIR, David worked on the new MOJO and the full
distribution provide quite the same thing.
We can guarantee a "standard" Karaf full distribution but not a custom
Karaf distribution.
Anyway, as I said in previous threads, as soon as Karaf 2.2.1 is out, we
will focus on trunk to deeper test the assemblies and new MOJOs.
I'm agree to include this kind of distribution (even if it could be a
large one :)).
Regards
JB
On 05/03/2011 08:46 PM, mikevan wrote:
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.
