> I have (on my experimental Maven 2 repository) every JARs not provided > in http://www.ibiblio.org/maven2 including Geotools JAR. I have also > setup our own project to links against those JARs. Users have a choice: > they can declare a dependency to "somemodule-2.2-SNAPSHOT.jar", in which > case Maven 2 checks once a day (by default, this is configurable) if a > new version is available. Or the users can declare a dependency to > "somemodule-2.2-20051010.224012-1.jar" (for example) where > "20051010.224012-1" has been automatically generated by Maven when we > executed "m2 deploy". This is actually quite easy. > This is not new, it is possible in Maven-1 and I setup a SNAPSHOT repository some time ago, we use it for GeoVISTA studio releases. You can see it at: http://dist.geotools.org/gt2/jars/
But yeah, the big difference is that Maven-1 checks for snapshots every single build for every module, which is a major pain! The main problem with that at the moment is that the server (codehaus) keeps timing out when cruisecontrol trys to upload the jars (this is the reason for most of the SNAPSHOT build failures, not true fails :( ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
