Good grief. We are compiling GeoTools twice for every Travis build. This
is a large part of the frequent Travis timeout failures we see.
Because GeoTools has a pom.xml in its root directory (note that
GeoServer does not), Travis detects it as a Maven project and tries to
resolve all dependenc
https://github.com/geotools/geotools/pull/1675
This change aligns GeoTools with GeoServer and allows GeoTools to be
built with MAVEN_OPTS=-Xmx512m (full build but not javadocs). Once
merged, I intend to backport to this change to all active branches and
configure MAVEN_OPTS=-Xmx512m on Travis.
Jens,
the master build passes for me with Maven 3.5.0 and OpenJDK 8u141 on
debian/sid. That is, I cannot reproduce a build failure on Linux.
I think the problem is that you need to "install" not "compile" to
ensure that all the metadata is generated.
Please try building with:
mvn -Dall cle
Hi Jody,
I have no idea how much work it is going to be. I wanted to run a first check
and generate the dependency tree with maven to check if any dependency needs
JSR275 because that would be a show-stopper. However, I have a problem building
geotools. I cloned the repo and did mvn compile,