[postgis-devel] PostGIS-JDBC

[Thomas Marti (HSR)]

As there seems to be no real interest by anyone else, we took the matter in our 
own hands. We chose some names we thought were appropriate and deploied the JARs 
to Refractions' Maven repo ourselves.

Versions 1.1.5 and 1.1.6 of the PostGIS-JDBC-Drivers are available at 
http://lists.refractions.net/m2/org/postgis

Maven users now can add this to their pom.xml:
============================================================
<repositories>
   <repository>
     <id>refractions</id>
     <name>Refractions Research Maven 2 Repository</name>
     <url>http://lists.refractions.net/m2</url>
   </repository>
</repositories>

<dependencies>
   <dependency>
     <groupId>org.postgis</groupId>
     <artifactId>postgis-jdbc</artifactId>
     <version>1.1.6</version>
     <scope>test</scope>
   </dependency>

   <dependency>
     <groupId>org.postgis</groupId>
     <artifactId>postgis-jdbc-jts</artifactId>
     <version>1.1.6</version>
     <scope>test</scope>
   </dependency>
</dependencies>
============================================================


Bye,
  Thomas & Stefan


Thomas Marti (HSR) schrieb:
> Hello everyone
> 
> 2) At the moment the only way to get the JDBC driver, is to either 
> download the sources and build it yourself or to install PostGIS and 
> then go dig for the JAR-file. In our opinion it would be much better to 
> have a separate download for that, as for example the PostgreSQL project 
> has (http://jdbc.postgresql.org/). Even better would be to put the JARs 
> in a public Maven repository, so Java developers would only have to put 
> the dependency in their POM files and the rest is then taken care of by 
> Maven.
> 
> We understand that this probably needs some time to be thought about, 
> but it would be very convenient for us if we had a decision on a naming 
> schema rather quickly. So that we won't have to change everything if you 
> eventually do decide to publish to a Maven repository. What is needed 
> for the names is a groupId (probably 'postgis' or 'org.postgis') and an 
> artifactId for every JAR (e.g. 'postgis'/'postgis_jts', 
> 'postgis-jdbc'/'postgis-jts-jdbc', 'postgis-driver'/'postgis-jts-driver' 
> or the like...)