| From the GeoServer mailing list:
Hi,
all builds of the 2.8.x series built with geootols jars off the repository (as opposed
to freshly built locally) are failing in the WMS module with several failures.
This for example breaks all Travis checks on 2.8.x (and of course the build
of anyone that is not accustomed to also build GeoTools locally). Looking into the issue I've found that the metadata.xml in the repository
is reporting the wrong snapshot version, see here: https://repo.boundlessgeo.com/main/org/geotools/gt-render/14-SNAPSHOT/maven-metadata.xml Here is the current content for reference in case it gets fixed later: <?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId>org.geotools</groupId>
<artifactId>gt-render</artifactId>
<version>14-SNAPSHOT</version>
<versioning>
<snapshot>
<timestamp>20151006.130203</timestamp>
<buildNumber>251</buildNumber>
</snapshot>
<lastUpdated>20160129113257</lastUpdated>
<snapshotVersions>
<snapshotVersion>
<classifier>sources</classifier>
<extension>jar</extension>
<value>14-20151006.130203-251</value>
<updated>20151006130203</updated>
</snapshotVersion>
<snapshotVersion>
<extension>jar</extension>
<value>14-20151006.130203-251</value>
<updated>20151006130203</updated>
</snapshotVersion>
<snapshotVersion>
<classifier>tests</classifier>
<extension>jar</extension>
<value>14-20151006.130203-251</value>
<updated>20151006130203</updated>
</snapshotVersion>
<snapshotVersion>
<extension>pom</extension>
<value>14-20151006.130203-251</value>
<updated>20151006130203</updated>
</snapshotVersion>
</snapshotVersions>
</versioning>
</metadata> It seems that while file gets updated (see <lastupdated>)
the snapshot tag does not get modified. The same is happening in other metadata.xml files, like for example,
in gt-main, we have the same situation (haven't checked others,
it might well be that they are all in the same situation). It's also worrysome that we have so many snapshots laying there,
eventually this will make the disk usage grow beyond the available
space The GeoServer jars/metadata.xml seem to be in the same situation,
and so do the GeoWebCache ones. The master series of the three projects instead looks up to date.
I diffed the pom files for the master and stable branches, but could
not see any relevant change. Searching on the internet, I've found this stackoverflow entry
that seems to be relevant: http://stackoverflow.com/questions/32353145/how-to-rebuild-maven-metadata-xml-in-artifactory I don't know if I have enough rights to execute this command, but even
if I could, I'd ask permission and check if people know of a better way.
Anyone has a better suggestion? About the amount of files piling up, Artifactory seems to have some
automatic cleanup procedures, but again I don't have enough rights
to reach to them (the admin/advanced area is grayed out for me, looks
like I'm not setup as an admin after all): https://www.jfrog.com/confluence/display/RTF/Managing+Disk+Space+Usage
|
