Eclipse updating indexes forever
You can disable this in the Maven configuration: Disable "Download Artifact Sources" and "Download Artifact Java Doc".You can also run mvn install from the console, which often solves these kinds of problems and less prone to errors during downloading.Installing into your local maven-repository means that maven downloads all dependencies from remote repositories into its local cache.Furthermore Maven complies your local sourcecode and creates packages in your local maven-repository.In order to tell Maven how to use it, you have to change your file, which can be found in | Please incorborate the instructions into this page Take a look for the walkthrough for Linux (adaptable for Windows as well).Please remind, for the WPS software you'll need additional repositories.You can try to force a redownload of the library by deleting the whole folder from the console, which often solves these kinds of problems and less prone to errors during downloading.The Maven-skin sources are located at: https://svn.52north.org/svn/52n/maven-skin/trunk Install the skin locally simply with If you are going to update the Maven-skin version, you will also have to update the 52n parent project located at: https://svn.52north.org/svn/52n/maven-root-project/trunk Install the parent locally with The basic layout for all community sites is generated using Apache Velocity (
Until today (2012-03-08) there are three communities, who build their sites with maven, Sensor Web, Geoprocessing and Security & Geo-RM.
If you want to debug the unit tests but still run them with Maven (for example because the tests need resource filtering), add the option . JCTree$JCField Access.accept(JCTree.java:1522) at tools. Maven should now re-download the library and hopefully install it properly.
There are detailed instructions how to build ogcschema with maven and xmlbeans: Maven Ogc Xmlbeans. If you check out a project for the first time, Eclipse and m2e might get stuck in a task (shon in the Progress view) called "Downloading Sources and Javadoc" for a long time, possibly forever.
They will have to delete it manually from their local maven repository first, to get the updated version from the 52n repository.
A more clean method to deploy an updated skin is to increase the version. Deploy the skin as described in the previous section.