Just like others, I would love EIK in Karaf repository. We would have one place where we have karaf-releated artifacts and one site with documentation.
Regarding the console/maven nature of Karaf - it still can be maven friendly as long as we'll port EIK to be build with tycho. We can start working on that in sandbox and once it will be done create a subproject. Regards, Lukasz > By now I've always used Karaf exclusive via mvn & console but I'm excited to > be convinced :-) Except for that the idea sounds very good to me. I'll give > the code a shot within the next days and come back with a more detailed > expression/feedback/opinion then :-) > > Kind regards, > Andreas > > On Wed, Aug 31, 2011 at 14:50, Jean-Baptiste Onofré <[email protected]> wrote: > >> Hi all, >> >> I discussed since few days with Stephen Evanchik, the author of EIK. >> >> EIK is currently an Eclipse lab project. >> EIK (Eclipse Integration for Karaf) is the integration of the Apache Karaf >> application platform and the Eclipse IDE. >> >> Notable features include: >> >> * An Eclipse Run/Debug launcher configuration that configures Karaf to >> run inside the workbench transparently to the developer >> * Automatic deployment of workspace plugin projects to running Karaf >> instances without copying files >> * A Target Platform Definition that allows developers to target only the >> bundles found in Karaf distributions >> * A Target Platform Provisioner that automatically constructs a target >> platform from any Karaf distribution on the user's local disk >> * JMX instrumentation of the Running/Debugging Karaf instance. >> * Eclipse views that display the Bundle and Service status of Karaf >> instances >> >> Experimental features: >> >> Web Tools Platform integration including: >> * Karaf server runtime with associated classpath maintenance >> * Karaf runtime locator that scans local disks for compatible Karaf >> distributions >> >> Stephen and I would like to propose EIK as a new Karaf sub-project. >> >> We're going to change the current license to use an Apache 2.0 license (I >> will take care of the IP-clearance), update the code base with the correct >> header files, etc. >> As for the others Karaf sub-project, EIK will use a SVN location like >> https://svn.apache.org/repos/**asf/karaf/eik<https://svn.apache.org/repos/asf/karaf/eik>(and >> an associated git repo). >> I will take care of others resources (Jira, Jenkins, Sonar, etc, etc :)). >> >> EIK could be a good platform for both Karaf development, but also to >> construct some tool on top of that (I can image some deployment or advanced >> monitoring "studios" powered by Eclipse/EIK, etc). >> >> This thread is not a vote, just a discussion thread. I would like to have >> your view about EIK before starting a formal vote. >> >> Thanks >> Regards >> JB >> -- >> Jean-Baptiste Onofré >> [email protected] >> http://blog.nanthrax.net >> Talend - http://www.talend.com >>
