Re: Maven Artifact JDK Suffix
| От | Vladimir Sitnikov |
|---|---|
| Тема | Re: Maven Artifact JDK Suffix |
| Дата | |
| Msg-id | CAB=Je-GNyGptoOJsD99Ag6pvGTr5gZ66xSqPZGXXEPkSwHcchA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Maven Artifact JDK Suffix (Sehrope Sarkuni <sehrope@jackdb.com>) |
| Ответы |
Re: Maven Artifact JDK Suffix
|
| Список | pgsql-jdbc |
>[2]: 9.4.1210.jre7 > 9.4.1207.jre8 So what is the problem with that? I do not think there is a "proper" way to compare 1210.jre7 vs 1207.jre8. I do not think it outweights "multiartifact" drawbacks I list below. What I fear is java 10 when we would hit a string literal comparison wall. Thus we might want use jre07, jre08, jre09 to be prepared for jre10 :) > They're entirely different artifacts They are not. For instance: is it sane to include _both_ artifacts at the same time? I do not think so. Having different artifact ids would: 1) Open can of worms with "multiple pgjdbc artifacts at the same time". 2) Make upgrading pgjdbc very hard. If jreX is a part of version, then you can define the version in parent pom, and all the child projects just inherit it. You can easily flip version back and forth by altering version in parent. If jreX is artifact id, then you would have to change all the child projects to use updated artifact id. Vladimir
В списке pgsql-jdbc по дате отправления: