I trigged a new build on Jenkins twice, but the discrepancy is still
present. There is an oddity with the Maven build that I have not yet
identified.
Could trying the trunk in the meantime be okay?
Martin
Le 27/11/15 14:17, Dieter Stüken a écrit :
> Hello,
> I just want to give current sis a try. When downloading the current snapshot
> I got a strange error.
> It was caused by
> https://repository.apache.org/content/repositories/snapshots/org/apache/sis/core/sis-referencing/0.7-jdk8-SNAPSHOT/maven-metadata.xml
> which declares <buildNumber>207</buildNumber> but refers to
> <value>0.7-jdk8-20151123.112634-206</value> instead.
> While using genuine maven it seems to work well. Unfortunately I have to use
> ivy/gradle which seems to use the build number instead of the referred name.
> Is it a temporary discrepancy?
> Conspicuously only even version numbers are generated. What about the odds.
> Dieter.
