Re: AW: PR-33: problems

2017-05-29 Thread Gintautas Grigelionis
Sorry for slow response, I'm on a trip. It does make sense to leave the exception in place only if ivy becomes opinionated about versions. I am not sure if compatibility break requires a change of major version. There are semver tools out there; maybe it's worth integrating them (redemption driven

AW: PR-33: problems

2017-05-29 Thread jhm
Sounds like I would do ;) I'll merge the PR locally and insert the delegates. Open is "src/java/org/apache/ivy/osgi/util/Version.java: the constructor removes the (IMO unneccessary) ParseException. But because it is a checked Exception we break BC." https://wiki.eclipse.org/Evolving_Java-ba

AW: PR-33: problems

2017-05-29 Thread jhm
Thanks, but I already have it done ;) But one point is open: src/java/org/apache/ivy/osgi/util/Version.java: the constructor removes the (IMO unneccessary) ParseException. But because it is a checked Exception we break BC. Jan > -Ursprüngliche Nachricht- > Von: Gintautas Grigelionis [