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"?> org.geotools gt-render 14-SNAPSHOT **** **20151006.130203** **251** **** 20160129113257 sources jar 14-20151006.130203-251 20151006130203 jar 14-20151006.130203-251 20151006130203 tests jar 14-20151006.130203-251 20151006130203 pom 14-20151006.130203-251 20151006130203It seems that while file gets updated (see )
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
So someone with proper rights will have to run this one.
Cheers
Andrea
···
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.