GitHub user janstey opened a pull request:
https://github.com/apache/karaf/pull/9
KARAF-2154 - Entering an empty command removes previous command in histo...
Patch for karaf-2.3.x branch.
You can merge this pull request into a Git repository by running:
$ git pull https://githu
It would be nice if Aries keeps up with its snapshot builds deployed
at apache snaphot repository, making early integration easier.
-D
On Thu, Jan 31, 2013 at 8:37 AM, Jean-Baptiste Onofré wrote:
> I did for some Aries bundles, but not all, my bad.
>
> I will take care of that on *all* Aries bu
I did for some Aries bundles, but not all, my bad.
I will take care of that on *all* Aries bundles next time.
Regards
JB
On 01/31/2013 05:27 PM, Dan Tran wrote:
To improve for next time, we may want to build with aries snaphot or
staging release to detect integration issue early
-D
On Thu, J
On Jan 31, 2013, at 11:27 AM, Dan Tran wrote:
> To improve for next time, we may want to build with aries snaphot or
> staging release to detect integration issue early
+1 - particularly if we're specifically waiting for fixes from Aries.
Dan
>
> -D
>
> On Thu, Jan 31, 2013 at 7:58 AM, Cl
To improve for next time, we may want to build with aries snaphot or
staging release to detect integration issue early
-D
On Thu, Jan 31, 2013 at 7:58 AM, Claus Ibsen wrote:
> On Thu, Jan 31, 2013 at 4:49 PM, Jean-Baptiste Onofré
> wrote:
>> I would prefer to propose a clean 2.3.1 fixing one o
On Thu, Jan 31, 2013 at 4:49 PM, Jean-Baptiste Onofré wrote:
> I would prefer to propose a clean 2.3.1 fixing one of the major issue in
> 2.3.0. I don't want to hurry to release 2.3.1 without the Aries fix.
>
> I'm sure that Dan will be able to cut off a new Aries release quickly.
> If it's take t
I would prefer to propose a clean 2.3.1 fixing one of the major issue in
2.3.0. I don't want to hurry to release 2.3.1 without the Aries fix.
I'm sure that Dan will be able to cut off a new Aries release quickly.
If it's take too much time, I will see how to move forward.
It's just a question o
On Thu, Jan 31, 2013 at 4:32 PM, Jean-Baptiste Onofré wrote:
> I updated Aries JMX, Blueprint, ... in Karaf 2.3.1-SNAPSHOT, but
> unfortunately, this Aries release introduced two new issues.
>
> I created the Jira and provide fixes, I'm afraid that it will require a new
> Aries release. Anyway, I'
I updated Aries JMX, Blueprint, ... in Karaf 2.3.1-SNAPSHOT, but
unfortunately, this Aries release introduced two new issues.
I created the Jira and provide fixes, I'm afraid that it will require a
new Aries release. Anyway, I'm investigating some workaround, but I
would prefer a clean Aries r
Hi
Any update on a Karaf 2.3.1 release?
--
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
10 matches
Mail list logo