Pavel Bodiachevskii

@amparo-siemens @gramss Put your bindings under https://github.com/asyncapi/spec-json-schemas/tree/master/bindings And create PR. Under it I'll review your changes and will provide further instructions upd: Bind them with each needed object, like this...

@fmvilas schemas were merged today https://github.com/asyncapi/spec-json-schemas/pull/582 What's next steps are? fyi: @derberg

> @fmvilas any update on the V3.1 minor release? 🙂 Release on me, my bad. I'll prepare needed things in a few days

@timonback this repo is destination point Start from creating PR in schemas repo - https://github.com/asyncapi/spec-json-schemas/tree/master/bindings/amqp Create new version 0.4.0 and change schema

@jonaslagoni @dalelane @smoya @GreenRover please, take a look this PR is ready https://github.com/asyncapi/spec-json-schemas/pull/555

> @jonaslagoni @dalelane @smoya @GreenRover please, take a look > > this PR is ready [asyncapi/spec-json-schemas#555](https://github.com/asyncapi/spec-json-schemas/pull/555) up @derberg @fmvilas @dalelane @smoya @char0n @GreenRover

> That said, I don't think we need to add every media type. It's really simple to define your own that can be used in your own code. Yep, agree...

> Just adding a string constant does not make it supported "out of the box", as JAX-RS does not mandate any implementation to provide Entity Providers for YAML. No problem,...

> > > Just adding a string constant does not make it supported "out of the box", as JAX-RS does not mandate any implementation to provide Entity Providers for YAML....

I already tried with -v flag, no warnings at all - log in message above. I compiled and launched client on intel based Mac