Re: [ANNOUNCE] Introducing Microbule...

Small update. Microbule 0.1.0 release has been cut and will soon be available in Maven Central (awaiting sync from Nexus OSS). Enjoy, folks! On Mon, Nov 21, 2016 at 1:03 PM James Carman wrote: > We've been working on a Microservices framework called "Microbule"

Re: [ANNOUNCE] Introducing Microbule...

super badly done website (pushed without fixing root context) but raw old draft (before renaming mi to mee) was here http://people.apache.org/~rmannibucau/microwave-snapshot/ Romain Manni-Bucau @rmannibucau | Blog | Old

Re: [ANNOUNCE] Introducing Microbule...

Very cool, Mark! I will check it out. Looks like it's focusing on Tomcat mostly at first glance. Is that right? On Mon, Nov 21, 2016 at 4:49 PM Mark Struberg wrote: > https://svn.apache.org/repos/asf/openwebbeans/meecrowave/trunk/ > > > Currently you need to manually

Re: [ANNOUNCE] Introducing Microbule...

https://svn.apache.org/repos/asf/openwebbeans/meecrowave/trunk/ Currently you need to manually compile the CXF 3.1.x-fixes branch first. Usage: just write an Appliaction and @ApplicationScoped @Path bean and add the meecrowave-maven-plugin org.apache.meecrowave

Re: [ANNOUNCE] Introducing Microbule...

I couldn't find anything on Meecrowave, but I would be interested in seeing the code. Where does it live? I tried googling On Mon, Nov 21, 2016 at 4:39 PM Sergey Beryozkin wrote: > Hi James > > Looks very promising, and I found the answer to the question I was about > to

Re: [ANNOUNCE] Introducing Microbule...

Hi James Looks very promising, and I found the answer to the question I was about to ask in a "What's in a Name" section at the end :-) Microbule, Meecrowave - the massive wave is coming :-) Cheers, Sergey On 21/11/16 18:11, James Carman wrote: The header names are configurable, so you

Re: [ANNOUNCE] Introducing Microbule...

By the way, I should give credit to Benson Margulies for giving me the "secret sauce" of creating CXF servers on-the-fly! Thanks, Benson! On Mon, Nov 21, 2016 at 1:03 PM James Carman wrote: > We've been working on a Microservices framework called "Microbule" which

Re: [ANNOUNCE] Introducing Microbule...

The header names are configurable, so you can use whatever you want. You just need to set up an etc/org.microbule.decorator.tracer.cfg file: traceIdHeader=My-Trace-ID requestIdHeader=My-Request-ID On Mon, Nov 21, 2016 at 1:09 PM Romain Manni-Bucau wrote: > Hi James, >

Re: [ANNOUNCE] Introducing Microbule...

Hi James, Would it be an option to extract the tracer - at least the names of the headers - to a "portable" module? With Mark we were on that area as well for meecrowave (a microprofile server based on CXF too and hosted @openwebbeans) and was thinking to add it to sirona since it is the

[ANNOUNCE] Introducing Microbule...

We've been working on a Microservices framework called "Microbule" which leverages CXF and Karaf (hence the cross-post): https://github.com/jwcarman/microbule The idea is to make writing Microservices easy and fun, by providing many of the oft-requested features for you out-of-the-box (CORS,

Re: [HEADS UP] Next releases

Yes, it's what I had in mind: 4.1.0 before Christmas. Regards JB On 11/21/2016 04:55 PM, Guillaume Nodet wrote: Maybe we should define a deadline so that we don't end up delaying 4.1.0 ad libitum. What about a 3 weeks deadline so we could plan a 4.1.0 on 12/12 ? 2016-11-21 16:27 GMT+01:00

Re: [HEADS UP] Next releases

Maybe we should define a deadline so that we don't end up delaying 4.1.0 ad libitum. What about a 3 weeks deadline so we could plan a 4.1.0 on 12/12 ? 2016-11-21 16:27 GMT+01:00 Achim Nierbeck : > Hi, > > we're working on the latest must fix for Pax-Web 6.0. So it might

Re: [HEADS UP] Next releases

Hi, we're working on the latest must fix for Pax-Web 6.0. So it might be good to have that in 4.1 too :) regards, Achim 2016-11-21 16:14 GMT+01:00 Guillaume Nodet : > 2016-11-21 14:17 GMT+01:00 Jean-Baptiste Onofré : > > > Hi guys, > > > > now that

Re: [HEADS UP] Next releases

2016-11-21 14:17 GMT+01:00 Jean-Baptiste Onofré : > Hi guys, > > now that ApacheCon is done, and regarding some dependencies new releases > (especially Pax URL 2.5.1), I think we can move forward on releases. > > I propose the following schedule: > > Karaf Container 4.0.8 by

Re: [HEADS UP] Next releases

+1. Thanks for your hard work. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Monday, November 21, 2016 2:17 PM, Jean-Baptiste Onofré

Re: [HEADS UP] Next releases

Hi guys, now that ApacheCon is done, and regarding some dependencies new releases (especially Pax URL 2.5.1), I think we can move forward on releases. I propose the following schedule: Karaf Container 4.0.8 by the end of this week. The important issue to fix is the support of ARM and

Re: Default log color ( was discussion at aries)

For me the main problem is that the default color is not the terminal color. The user can easily tune the terminal color and background on his terminal client but he can not tune our special colors there. No color is good if you want to completely work without the colors but I think the more

Re: Default log color ( was discussion at aries)

I think we should add a few snapshots to the jira to see several options. In particular, the theme should be seen on both black and white terminals to see what it gives. Here are a few possibilities: https://jeanchristophegay.com/de-la-couleur-dans-les-logs/ I like this one which should be

Re: Default log color ( was discussion at aries)

Hi Christian, I'm a bit surprised as the --no-color is always possible and you can also create an alias. So, if the issue is color or not color, I would recommend just a --no-color alias. If the colors themselves, then, no problem to use term colors and so create a Jira. Regards JB On

Default log color ( was discussion at aries)

I fully agree with Brad that the default color is not very readable. It also makes it difficult for users to change their terminal colors on their client. So I propose we change the default log color to the default terminal color and only use other colors to highlight special things like