I experimented with this today as a background activity; sorry for all the
noise from the build box.
It looks to be differences in how to encode spaces in "GeoTools 29
Releases" folder, various combinations of quotes and spaces are
recommended, command line options (s / --protect-args) to prevent
Oh sorry this is the source forge upload, perhaps source forge directory
structure changed - do we have a new location in mind?
Jody
On Wed, Jul 19, 2023 at 3:23 AM Ian Turton wrote:
> I'm fairly sure we ran into this last time too, it seems that the project
> directory has moved, looking at th
Something indeed moved recently, Torben was working on it with the system
admin committee.
Perhaps check the other documentation builds? I am sure we just did not
think about the release documentation being uploaded int the same fashion.
Jody
On Wed, Jul 19, 2023 at 3:23 AM Ian Turton wrote:
>
I'm fairly sure we ran into this last time too, it seems that the project
directory has moved, looking at the docs (
https://sourceforge.net/p/forge/documentation/rsync/) it seems that aiming
for
/home/frs/project/geotools/29.2/
Is this a fix that needs to go into main and be backported? Or is it
Just a guess: you have in the classpath, first a JRE 11, then a JDK 17. The
first one provides the java, but does not have a javac, which is
being provided by Java 17 instead.
Cheers
Andrea
On Wed, Jul 19, 2023 at 9:24 AM Ian Turton wrote:
>
>
> On Tue, 18 Jul 2023 at 18:53, Jody Garnett wrote
On Tue, 18 Jul 2023 at 18:53, Jody Garnett wrote:
> Ian, the same test works for me locally. I expect you are mixing up java
> compilers on your local machine when testing.
>
You're right I do seem to be using Javac 17 and Java 11 - no idea why
though.
Ian
>
> The rest of the bin download look
