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 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? >> groupId="org.geotools.jdbc" artifactId="gt-jdbc-db2" >> groupId="org.geotools" artifactId="gt-jdbc-mysql" >> groupId="org.geotools.jdbc" artifactId="gt-jdbc-oracle" >> groupId="org.geotools.jdbc" artifactId="gt-jdbc-postgis" >> Is there any method to this madness? > > I don't think there is... but I see just one error in the groupId > of the mysql module. Where's the rest of the madness? > > Cheers > Andrea > > -- > Andrea Aime > OpenGeo - http://opengeo.org > Expert service straight from the developers. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
