I am not how it makes sense myself ... when I do a mvn deploy it goes
to:
- Uploading:
http://download.osgeo.org/webdav/geotools//org/geotools/gt-jdbc-mysql/2.6-M2/
And creates the following pom:
org.geotools
gt-jdbc-mysql
jar
MySQL DataStore
So my guess is the pom.xml for this one need
Jody Garnett ha scritto:
> The groupId for the mysql module is actually correct - that is what
> 2.6-M2 deployed it as...
I don't see how it can be correct. The jdbc-ng modules are a sub-group,
their group id should specify that just as it happens with
the xml modules, "org.geotools.xsd".
Please
The groupId for the mysql module is actually correct - that is what
2.6-M2 deployed it as...
Hunting through the maven repository trying to make sense of things
turned up several other older combinations using /jdbc gt-jdbc/ etc
Jody
On 25/08/2009, at 5:26 PM, Andrea Aime wrote:
> Jody G
Jody Garnett ha scritto:
> I have been have a spot of fun untangling jdbc-ng artifact dependencies
> - since switching to 2.6-M2. When working with SNAPSHTOTs almost
> everything was available (since we have published a SNAPSHOT over the
> last several months). Can we clean out old SNAPSHOTs?
>
I have been have a spot of fun untangling jdbc-ng artifact
dependencies - since switching to 2.6-M2. When working with SNAPSHTOTs
almost everything was available (since we have published a SNAPSHOT
over the last several months). Can we clean out old SNAPSHOTs?
groupId="org.geotools.jdbc" ar
