Jérémie Bresson

I found an other case where a POM on maven central contains multiple version ranges: [`plugin-node-resolve-15.2.3.pom`](https://repo1.maven.org/maven2/org/mvnpm/at/rollup/plugin-node-resolve/15.2.3/plugin-node-resolve-15.2.3.pom) ```xml org.mvnpm rollup [2.78.0,3),[3.0.0,4),[4.0.0,5) ``` (using the `${org.mvnpm-rollup.version}` variable that I have resolved here)...

From the maven docs: > Multiple requirements are separated by commas. sources: https://maven.apache.org/pom.html#Dependency_Version_Requirement_Specification

Until this is sorted out, I have released this version on maven central: ```xml com.unblu.ua-parser uap-java 2.0.0 ``` From the fork https://github.com/unblu/uap-java It contains the change suggested in this PR.

A PR can be submitted to add it

This is really a good idea, I have created https://github.com/ua-parser/uap-java/pull/83 for that.

If you are interested by this idea, I have released this version on maven central: ```xml com.unblu.ua-parser uap-java 2.0.0 ``` From the fork https://github.com/unblu/uap-java

I agree, you can even go to `0.9.6` as suggested in https://github.com/web-push-libs/webpush-java/pull/192

Yes it is still on my TODO list to review this. Sorry for the delay.

Thank you very much for this contribution 🎉

I think the example app shared by @alerosmile https://github.com/alerosmile/vert.x-grpc-cancellation-test is demonstrating exactly the problem we are interested in. Run `mvn verify` to generate the java code corresponding to the proto....