Description of problem: The pom.xml data and the mvn() Provides are incorrect. The group isn't "postgresql", but "org.postgresql" in the pom.xml from Maven Central Repository[0]. Also, those that register for the jdbc41 version[1] (which is what you're supposed to use for Java 7/8 software) don't get anything from our package because it's not registered as such. There may be other errors, but I noticed these right off the bat. [0]: http://repo1.maven.org/maven2/org/postgresql/postgresql/9.4-1200-jdbc4/postgresql-9.4-1200-jdbc4.pom [1]: http://repo1.maven.org/maven2/org/postgresql/postgresql/9.4-1200-jdbc41/postgresql-9.4-1200-jdbc41.pom Version-Release number of selected component (if applicable): 9.4.1200-1.fc22 How reproducible: Always
Created attachment 1066751 [details] changes group id in pom.xml If I understand correctly, you want different group id in pom.xml. I would like to ask you for review of attached patch. I am not sure how many users will be affected by this change.
Sorry about taking so long to get to this, but yes this patch looks correct.
Comment on attachment 1066751 [details] changes group id in pom.xml Oops, it wasn't for me to review. But it looks good to me, and I'm restoring the review request.
We are working on this with upstream. Anybody interested/concerned is welcome to contribute to usptream discussion: http://www.postgresql.org/message-id/CADK3HHLbiCyZnfxqwj=60L1kANhPuBFtv0kZ68Znubugj1gE7g@mail.gmail.com Sorry for the delay, btw. It's been long time postgresql-jdbc has not been updated and it should happen soon. Until that time -- I do not plan to change the build system issues because the build system was completely reworked in upstream and we need to adopt it first.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Hi Neal, actual 'master' branch (will be soon built) provides: mvn(org.postgresql:postgresql:pom:) = 9.4.1209 mvn(postgresql:postgresql) = 9.4.1209 mvn(postgresql:postgresql:pom:) = 9.4.1209 osgi(org.postgresql.jdbc42) = 9.4.1209 postgresql-jdbc = 9.4.1209-3 Does that make sense? It looks like we could close this bug, but I'm rather asking.
Comment on attachment 1066751 [details] changes group id in pom.xml Clearing 'review?' flag, the patch doesn't apply anymore.
I'm closing this bug because I believe that the provides are fine now, at least the 'org.postgresql.*' namespace is provided too - which is IMO equivalent to effect of attachment 1066751 [details]. Feel free to reopen if I'm wrong. Thanks!