[Geoserver-devel] Geoserver 2.11.0 release pom.xml in project sources

Hello everybody,

I just downloaded the released geoserver 2.11.0 project sources and see that the project pom.xml still contains 2.11-SNAPSHOT as version number instead of 2.11.0.
Does anybody knows why it is the case? Can I simply change the parent project version from 2.11-SNAPSHOT to 2.11.0 to get desired maven dependencies?

The released geotools project pom.xml has the correct version 17.0 (not 17-SNAPSHOT) by the way.

Mit freundlichen Grüßen / Kind regards

Hervé Minko
Software Ingenieur / Software Engineer

Mettenmeier GmbH
Klingenderstr. 10 - 14
33100 Paderborn, Germany

T +49 5251 150-307
F +49 5251 150-366
M +49 173 6025631
E herve.minko@anonymised.com
I www.mettenmeier.de

Mettenmeier GmbHXING - Mettenmeier GmbHFacebook - Mettenmeier GmbHYouTube - Mettenmeier GmbHTwitter - Mettenmeier GmbH

_______________________________________________________

Mettenmeier GmbH
Sitz der Gesellschaft: 33100 Paderborn
Geschaeftsfuehrung: Ulrich Mettenmeier
Handelsregister: Amtsgericht Paderborn B 1114
USt.-ID: DE 811 324 124
Steuer-Nr.: 339/5873/3133
_______________________________________________________

On Mon, Mar 27, 2017 at 11:13 AM, <Herve.Minko@anonymised.com> wrote:

Hello everybody,

I just downloaded the released geoserver 2.11.0 project sources and see
that the project pom.xml still contains 2.11-SNAPSHOT as version number
instead of 2.11.0.
Does anybody knows why it is the case?

Confirmed, it's like that in the tag as well:
https://github.com/geoserver/geoserver/tree/2.11.0

However the 2.10.2 release does not have the same problem, and the
automated release scripts are supposedly the same.
Humm... that might be cause the release build failed at one point trying to
start the generation of the windows/osx installers.
We probably want to modify those scripts to fist commit and then start the
remote jenkins jobs doing the installers:

https://github.com/geoserver/geoserver/blob/2.11.0/build/build_release.sh#L361

Can I simply change the parent project version from 2.11-SNAPSHOT to
2.11.0 to get desired maven dependencies?

Probably so, yes

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 di Montramito 3/A
55054 Massarosa (LU)
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.

-------------------------------------------------------