Clint Lewis a écrit :
Is there anyway I could turn off these lookup for the pom files that are associated with the jars?
I have put the jars into the correct place but I have not yet created the poms, so when I do a mvn compile it takes for ever looking for a few hundred pom's
Downloading: file://R:/m2/repository/batik/batik-svggen/1.1.1/batik-svggen-1.1.1.pom
[WARNING] Unable to get resource from repository repos (file://R:/m2/repository)
I believe that you need to create the pom.xml file. You don't need to create it by yourself. You can pick up one there (for version 1.5 and above):
http://www.ibiblio.org/maven2/batik/batik-svggen/1.6/
Actually, the easiest may be to not copy those files in a custom repository, since they already exists on ibiblio. You can do the following approach (this is what Geotools Maven 2 build currently does):
1) Make sure that the following exists in yours parent pom.xml file:
<repositories>
<repository>
<id>ibiblio</id>
<name>Ibiblio - the public's library and digital archive</name>
<url>http://www.ibiblio.org/maven2</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
... etc ...
</repositories>
2) When you are looking for a dependency, first check if the JAR file is already available at http://www.ibiblio.org/maven2/. If it is (like batik-svggen version 1.5 and 1.6), then you are done. If it is not, then you need to upload both the JAR file and the pom.xml file in yours own repository, and create the .md5 files if you want to avoid warnings everytime Maven download a file. You can also link toward an additional repository which provide the missing JAR, e.g. http://maven.geotools.fr/repository/. The idea is to upload in custom repositories only the JAR files not found in ibiblio. Note that you can specify as many repositories as you want in the <repositories> section.
The mean reason I can see for not using ibiblio is that www.ibiblio.org is not always very reliable. Connections are often lost during download. However, because the downloads are done only once (or when the version increment), it may not be that much painful. If a download fail, user just need to restart "mvn install" again and again until all download succeed, and from that point he is okay until a version is incremented. Giving all the pain that it save us from maintaining ourself something like www.ibiblio.org/maven2, doing "mvn install" more than once until the first successful build may be a minor pain.
Martin.