Re: Maven Artifact JDK Suffix

On Fri, Jan 15, 2016 at 8:50 AM, Vladimir Sitnikov <
sitnikov(dot)vladimir(at)gmail(dot)com> wrote:

> >Using two digits won't fix anything
>
> Well, if one module depends on "jre9 and another depends on jre10",
> then jre9 will be used by Maven.
>

That would only happen if both the jre9 and jre10 versions specified were
the same release version. A later jre9 release would still be picked over
an earlier jre10 release as the release version is on the prefix.

> Another issue: maven badge would display wrong version.
>
> https://maven-badges.herokuapp.com/maven-central/org.postgresql/postgresql/badge.svg
>
> >looks odd compared to how JRE versions are generally referred.
>

Why not change the JRE suffix into a prefix?

Sure it looks ever weirder but it does have the advantage of sorting
properly. From a feature perspective, a newer JDK version would be
considered a superset of an older JDK version (as it'd sort later). We
would still need to switch to a double digit to ensure proper sorting.

Here are some examples:

* jre07-9.4.1207
* jre08-9.4.1202
* jre09-9.4.1204
* jre10-9.4.1205

With this setup the JRE comes first so the newer JRE-based driver version
always wins. That would fix newer JDBC features mysteriously disappearing
when a dependency adds a newer driver version for an older JRE.

Regards,
-- Sehrope Sarkuni
Founder & CEO | JackDB, Inc. | https://www.jackdb.com/