I am looking at the difference between - and I am afraid aggregated
javadocs need to be removed (or get their own profile) - I need
unsupported/geometry to build (and the direct dependency in the root
pom.xml is in my way):
trunk/pom.xml
>
> <!-- =========================================================== -->
> <!-- Dependencies to be inherited by all modules. -->
> <!-- In some previous Geotools version, those dependencies -->
> <!-- were specified in module pom.xml. However, experience -->
> <!-- that aggregated javadoc fails if the GeoAPI dependency -->
> <!-- is not specified at this level. -->
> <!-- =========================================================== -->
> <dependencies>
> <dependency>
> <groupId>org.opengis</groupId>
> <artifactId>geoapi-nogenerics</artifactId>
> <!-- The version number is specified above. -->
> </dependency>
And geometry/pom.xml:
> <dependency>
> <groupId>org.geotools</groupId>
> <artifactId>gt2-main</artifactId>
> <version>${project.version}</version>
> <exclusions>
> <exclusion>
> <groupId>org.opengis</groupId>
> <artifactId>geoapi-nogenerics</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
