I have a small question regarding synching from svn to website, would this be automated or only done as a release process? I ask only in that an errant commit to such a file could cause problems to Karaf instances in production until caught and resolved. Follow on question; do we pgp sign (or the like) this file and validate Karaf side? Perhaps I'm over thinking the proposal, I'm just trying to ensure we don't inadvertently open vulnerability.
Cheers, Jamie On Fri, May 6, 2011 at 7:56 PM, Guillaume Nodet <gno...@gmail.com> wrote: > I think the dependency problem is common to all projects that provide > karaf extensions such as commands. > I really think the way to go is to have karaf pointint to an external > file from karaf web site as I explained in the other thread. That way > we could reference camel and other projects too. > > I propose to host in subversion the following: > karaf/repository/karaf-2.2.xml > and > karaf/repository/karaf-3.0.xml > > The whole karaf/repository folder would be synced from svn into > http://karaf.apache.org/repository/ > We then need to change 2.2.x and 3.x branches to add the respective > file as a feature repository. > These files would only contain links to other compatible repository > descriptors: > > <features name="karaf-global-${project.version}" > xmlns="http://karaf.apache.org/xmlns/features/v1.0.0";> > <repository>url-to-another-repository</repository> > ... > </features> > > If we agree on that, I think we should also trim down a bit the > standard descriptor to remove any non core-karaf related features > (such as spring, spring-dm, spring-web, and even war). Those would be > pushed along with the aries related features from the enterprise > descriptor and cellar feature to this global repository. > We can then add to this repo any other open source project that > provides features such as cxf, camel, activemq (and hopefully others > to come). > > The only thing would be to make sure that if there's no internet > connection, karaf still works nicely and that those repositories can > be lazy loaded so as to not slow down karaf startup when the > descriptor becomes bigger. > > > On Fri, May 6, 2011 at 23:59, Ioannis Canellos <ioca...@gmail.com> wrote: >> I have committed Cellar as a subproject, so that it can have its own release >> cycle: https://svn.apache.org/repos/asf/karaf/cellar/ >> Once we make our first release we can add the Cellar features as part of the >> standard or enterprise features, as discussed. However, we still need to see >> how we are going to implement this, since cellar depends on Karaf. >> >> For now let's create the subproject to Jira. Jean Baptiste can you do it? >> Jamie, could you help me with the release management issues? >> >> -- >> *Ioannis Canellos* >> * >> http://iocanel.blogspot.com >> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC >> Apache ServiceMix <http://servicemix.apache.org/> Committer >> * >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > > Connect at CamelOne May 24-26 > The Open Source Integration Conference > http://camelone.com/ >
