Readme.md doesn't reflect state of repo

[PatrikSteuer]

Problem

The readme states that a trace propagation via the w3c headers is possible. However the mentioned property opentracing.jaeger.enable-w3c-propagation does not work with the latest (3.2.2) version due to a #107 which reverted several commits before releasing.

This is a state which causes confusion.

Solutions

1. Adopt readme and remove the w3c trace propagation
2. Add commits reverted by Bump Spring Boot to 2.3.4.Release for Jaeger 1.1 #107 and release a new version

Due to the need for the w3c trace propagation I would favour the second approach.

[geoand]

You are right!

Can you please remind me towards the end of the week to do a new release as to implement solution 2?

Thanks

[PatrikSteuer]

Hi @geoand,
this is your friendly reminder to release a new version, including the w3c trace propagation.
Best
Patrik

[poznachowski]

Hey! Is there any ETA on upgrading jager-client to 1.3.2 ?

[geoand]

Hi,

I just opened #119 to bump the client.

Once that is in, I'll do a new release

[poznachowski]

Thanks! How long does it take for the new release to be available on Maven central ?

[geoand]

You are welcome.

It usually takes around 24 hours to sync to Maven Central