Re: [Proposal] Start 3.0.x stabilizing branch and feature freeze

From my point of view everything I need is in trunk already. Whenever we discussed what should be in 3.0 there were always some features people wanted to have. If we can agree that we are feature complete already I am also +1 Christian Am 14.01.2012 18:19, schrieb David Jencks: We've been fea

Re: Karaf Jetty feature in branch 2.2.x

I've applied your patch in revision 1231633 [1]. Thank you very much for the patch and for spotting this. Kind regards, Andreas [1] https://svn.apache.org/viewvc?view=revision&revision=1231633 On Sat, Jan 14, 2012 at 23:40, Christian Müller wrote: > JIRA created [1] and patch attached. > > [1]

Re: Karaf Jetty feature in branch 2.2.x

JIRA created [1] and patch attached. [1] https://issues.apache.org/jira/browse/KARAF-1153 Best, Christian On Sat, Jan 14, 2012 at 6:45 PM, Andreas Pieber wrote: > nope, there is no reason for that; if the bundle is required feel free to > create a JIRA/provide a patch for the features.xml. > >

Re: Issue with the latest mvn change on trunk

When I removed settings.xml (with mirror settings) I found the syntax of the mvn repo list was wrong and only the startup bundles would start. I committed a fix. Now (almost) all the bundles start for me and aether is using the karaf system repo. On my dev machine all the bundles start. On a

Re: Issue with the latest mvn change on trunk

It's what I did: - git clone && mvn clean install -DskipTests on ops4j base, swissbox, url - mvn clean install -DskipTests on Karaf on two different environments, same behavior. I'm performing new tests/builds and keep you posted. Regards JB On 01/14/2012 06:15 PM, David Jencks wrote: I track

Re: Karaf Jetty feature in branch 2.2.x

nope, there is no reason for that; if the bundle is required feel free to create a JIRA/provide a patch for the features.xml. Kind regards, Andreas On Sat, Jan 14, 2012 at 18:41, Christian Müller wrote: > Hello guys! > > Is there any reason why the jetty feature in the branch 2.2.x not include

Karaf Jetty feature in branch 2.2.x

Hello guys! Is there any reason why the jetty feature in the branch 2.2.x not include the jetty-websocket bundle? The current trunk has this bundle in the Jetty features description. I'm asking because a newly added component, Camel websocket, failed because of this missing dependency (tested with

Re: [Proposal] Start 3.0.x stabilizing branch and feature freeze

We've been feature complete since last august, except everyone keeps deciding we need more features. I think Andreas's point is that unless we decide that we're going to do a release we'll never run out of essential features that absolutely need to be in 3.0 before we can release it. What spec

Re: Issue with the latest mvn change on trunk

I tracked down all the snapshots now needed for pax url and built base swissbox url karaf With settings.xml in place using local nexus as a mirror I don't see that exception and karaf.log shows entries like 2012-01-14 09:00:44,943 | INFO | rint Extender: 3 | AetherBasedResolver |

Re: [Proposal] Start 3.0.x stabilizing branch and feature freeze

Basically this is a good idea. I am just unsure if we are already at the point where we should do the branch. Do we have all features necessary for 3.0 finished? I think we should do the branch as soon as we are feature complete. So the branch really can focus on stabilizing things. Christian

Re: [Proposal] Start 3.0.x stabilizing branch and feature freeze

+1 I think taking this step will really help focus our community effort, and provide clear guidance as to when/where to expect new features to appear. Cheers, Jamie On Sat, Jan 14, 2012 at 12:10 PM, Andreas Pieber wrote: > Hey guys, > > As all of you know we really want to get Karaf 3.0 out now

[Proposal] Start 3.0.x stabilizing branch and feature freeze

Hey guys, As all of you know we really want to get Karaf 3.0 out now for some time. But as long we add new "groundbreaking" features to the master we'll always destabilize it at some point. To give us a chance to finally stabilize the entire thing and getting out a 3.0 release I would like to prop

Re: Issue with the latest mvn change on trunk

Another issue that we have to address is the startup time. Karaf 2.2.x is very quick to start (something like 5 seconds on my machine), whereas Karaf 3.0.0 is very long (I got the shell in around 5 seconds, but to have all services available (features, etc), it takes something like 1mn, we can

Re: Issue with the latest mvn change on trunk

Hi David, I built Pax URL 1.4-SNAPSHOT on my machine (with a fresh git pull). And I have exactly the same issue. Moreover I have another issue at startup: ERROR: Bundle org.ops4j.pax.url.wrap [2] Error starting mvn:org.ops4j.pax.url/pax-url-wrap/1.4-SNAPSHOT (org.osgi.framework.BundleExceptio

Re: Database commands for Karaf

I agree with Andreas here. I think that they are beyond Karaf's scope. Maybe they should be part of ServiceMix or an other project. -- *Ioannis Canellos* * FuseSource ** Blog: http://iocanel.blogspot.com ** Apache Karaf Committer & PMC Apache Ca

Re: Database commands for Karaf

I really like those ideas. Both of them, but I'm not sure if Karaf is the right location for them. I think it would be better to locate them at the target projects if possible (amq, aries, ...) or create Karaf subprojects if this is not possible. But I've no problem with including them into e.g. th