Andrea, you will be pleased to know that I have just switched all the application schema resource bundle artifacts (and their consumers) over to using a single version rather than a version range.
The main reason for this change is that, after further thought, I realised that it is unsafe to have unpinned dependencies of a fixed-version release. For example, Jody could tag 2.7-M3 and then I could break it with a bungled geosciml-2.0 artifact update, removing repeatability of builds. Version ranges are a bit to snapshottish[1] to be repeatable dependencies. Not to mention their snapshottish check-for-updates behaviour, which was causing your intermittent build problem. So although we never got to the bottom of your build problem, it did make me think a bit more about version ranges, and whether they were worth it (answer: no). Kind regards, Ben. [1] Yes, this is a new word that I invented just now. On 30/06/10 17:42, Ben Caradoc-Davies wrote: > Andrea, > > I am surprised to see this. I have never seen this failure. What version > of maven are you using? Do you have a local time problem? Why would a > forced-update work when you should already have the artifacts in your > local repo? > > I understand that my use of version ranges causes artifacts to be > treated a bit more like snapshots, as maven looks for later versions in > the range. I am considering changing all of of them to single versions > and redeploying. I am trying to avoid this because it means any change > to a low-level artifact requires changing all artifacts that depend on it. > > I'd love to know why this is failing for you. If we can't figure it out > and fix it, I'll change the artifacts. (I am pretty much stuck in > meetings until next week.) > > Kind regards, > Ben. > > > On 25/06/10 14:57, Andrea Aime wrote: >> Hi, >> every day I build Geotools, and every day I get this: >> >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] BUILD ERROR >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Failed to resolve artifact. >> >> No versions are present in the repository for the artifact with a range >> [1.0.1,1.0.2) >> net.opengis.schemas:sweCommon-1.0.1:jar:null >> >> from the specified remote repositories: >> central (http://repo1.maven.org/maven2), >> maven2-repository.dev.java.net (http://download.java.net/maven/2), >> opengeo (http://repo.opengeo.org), >> osgeo (http://download.osgeo.org/webdav/geotools/) >> >> Path to dependency: >> 1) org.geotools:gt-app-schema-resolver:jar:2.7-SNAPSHOT >> 2) org.geosciml:geosciml-2.0:jar:2.0.2-1 >> 3) net.opengis.schemas:sampling-1.0:jar:1.0.0-1 >> 4) net.opengis.schemas:om-1.0:jar:1.0.0-1 >> 5) net.opengis.schemas:sensorML-1.0.1:jar:1.0.1-1 >> >> >> >> The workardound so far has been to add -U to the build command, >> mimicking what the build server does, but it makes the build >> quite a bit slower... >> Is there anything that can be done to avoid it? >> >> Cheers >> Andrea >> > > -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
