-1; for embedding this external feature into karaf
+1 on the central "knowledge" base about external features available :)
One side node, OpenEJB with Karaf, Interesting something I always wanted
to try :)
Also -1; I'm also for the repository approach! (I've also added something like
this already to the roadmap page)
kind regards,
andreas
On Fri, Feb 11, 2011 at 07:37:52PM +0100, Guillaume Nodet wrote:
-1 If they have it, why would we copy it and have to maintain it. We
can simply point users to it, can't we ?
I don't really want to maintain a feature file for all projects people
could be interested in, that doesn't scale and will only add more
dependencies and problems to our builds. I'd like to push the aries
one back to aries too.
However, having a wiki page or a non released file we could features
repository file that would have links to other repositories would be
fine imho.
For example, we could imagine having somewhere a repository with only
other repositories in it. Users coud just add that one and that would
give them access to lots of projects.
On Fri, Feb 11, 2011 at 18:15, Charles Moulliard<[email protected]> wrote:
Hi,
OpenEJB project has created a feature file to deploy their bundles.
This should be an excellent candidate for our Enterprise Features file
and a compagnion for Aries. Is it better to copy / paste their
features in our file or to point to their feature file in
org.apache.karaf.features.cfg ?
+ 1 : to copy/paste = add their file in karaf.features.cfg
- 1 : to copy/paste = add their file in karaf.features.cfg
Regards,
Charles Moulliard
Sr. Principal Solution Architect - FuseSource
Apache Committer
Blog : http://cmoulliard.blogspot.com
Twitter : http://twitter.com/cmoulliard
Linkedin : http://www.linkedin.com/in/charlesmoulliard
Skype: cmoulliard
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
