Thanks Jody, apologies for not spotting your existing ticket. Regards,
Aaron Sedgmen. From: Jody Garnett <jody.garn...@gmail.com> Sent: Friday, 24 February 2023 2:11 PM To: Aaron Sedgmen <aaron.sedg...@ga.gov.au> Cc: Geoserver-users@lists.sourceforge.net Subject: Re: [Geoserver-users] Build Information contains unresolved tokens [SEC=OFFICIAL] I made a ticket for this and also found the cause: https://osgeo-org.atlassian.net/browse/GEOS-10871 It is indeed a build issue. The -Prelease profile engages a version 1.7 of antrun that supports targets. Without this profile antrun 1.3 was used that expects tasks. The latest is antrun 3 :) Jody On Thu, Feb 23, 2023 at 4:32 PM Aaron Sedgmen <aaron.sedg...@ga.gov.au<mailto:aaron.sedg...@ga.gov.au>> wrote: Hi all, When running a GeoServer WAR packaged from the osgeo nexus repository, the Build Information in the About GeoServer page of the GUI contains unresolved tokens for the GeoServer Version (@project.version@), GIT Revision (@build.revision@) and Build Date (@build.timestamp@). I suspect this is due to the GeoServerApplication.properties file in gs-web-core.jar<https://repo.osgeo.org/#browse/browse:Geoserver-releases:org%2Fgeoserver%2Fweb%2Fgs-web-core%2F2.22.2%2Fgs-web-core-2.22.2.jar> containing unresolved tokens for those properties, which occurs in releases 2.22.1 and 2.22.2, although earlier releases are ok. Before creating a ticket, I’m wondering if the unresolved tokens in the GeoServerApplication.properties file is a red herring and there’s something else that I’m missing? Regards, Aaron Sedgmen Geoscience Australia Disclaimer: This e-mail (and files transmitted with it) is intended only for the person or entity to which it is addressed. If you are not the intended recipient, then you have received this e-mail by mistake and any use, dissemination, forwarding, printing or copying of this e-mail and its file attachments is prohibited. The security of emails transmitted cannot be guaranteed; by forwarding or replying to this email, you acknowledge and accept these risks. _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/geoserver-users -- -- Jody Garnett Geoscience Australia Disclaimer: This e-mail (and files transmitted with it) is intended only for the person or entity to which it is addressed. If you are not the intended recipient, then you have received this e-mail by mistake and any use, dissemination, forwarding, printing or copying of this e-mail and its file attachments is prohibited. The security of emails transmitted cannot be guaranteed; by forwarding or replying to this email, you acknowledge and accept these risks.
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
