Opened 11 years ago

Closed 10 years ago

#1006 closed defect (wontfix)

Change the scope of postgis-stubs dependency in postgis-jdbc Maven pom to "provided".

Reported by: cheidmann Owned by: delawen
Priority: critical Milestone: PostGIS 1.3.7
Component: postgis Version: 1.3.X
Keywords: maven Cc:

Description

At the moment org.postgis:postgis-jdbc:1.3.3 includes org.postgis:postgis-stubs:1.3.3 as compile-dependency:

postgis-jdbc-1.3.3.pom:

<dependency>
	<groupId>org.postgis</groupId>
	<artifactId>postgis-stubs</artifactId>
	<version>1.3.3</version>
	<scope>compile</scope>
</dependency>

The "compile" scope is incorrect here, it should be "provided". The "compile" scope means "dependency is required to compile and also needed in the run-time". The "provided" means "dependency is required to compile but we are sure it will be provided in runtime".

Having "compile" instead of "provided" effectively adds the "postgis-stubs" JAR to the classpath of the application which is not correct and leads to problems like explained here:

http://postgis.refractions.net/pipermail/postgis-users/2005-March/007153.html

Change History (3)

comment:1 Changed 11 years ago by pramsey

Milestone: PostGIS 2.0.0PostGIS 1.3.7

This problem doesn't exist in truck (there is no pom anymore!) I've pushed it backwards

comment:2 Changed 10 years ago by pramsey

Owner: changed from pramsey to delawen

comment:3 Changed 10 years ago by delawen

Resolution: wontfix
Status: newclosed

Those builds where built with a different pom.xml than the one on the trunk. It shouldn't be a problem now.

Note: See TracTickets for help on using tickets.