I know this issue well… I think I am actually be the cause of it :) And
yes, I have this issue consisently on osx and windows, linux seems to
handle it a bit more gracefully.
I think your (2) question hints at the best solution going forward (at
least that was the consensus the last time we discussed it iirc), and that
is not to use the name of the directory as the absolute source of the
feature type name, instead use what you find in the featuretype.xml config
file. This would allow us to encode the directory names in a more
universally file system friendly way, but still support feature types with
“extended characters” in them.
Perhaps that is easier now with the recent work done to abstract away raw
resource access, not sure.
$0.02
On November 28, 2017 at 11:15:24 AM, Torben Barsballe (
[email protected]) wrote:
Hello All,
In the past week or so, I've been running into some issues with some of the
new files added under /data, namely the two versions of "
data/citensg-1.0/workspaces/sf/sf/EntitéGénérique"
As far as I can determine, there are two folders named the same thing,
differing only in the unicode encoding of the "é".
Some filesystems, including the macOS filesystem, don't like this (similar
to case-sensitive files).
Locally, these two folders are treated as the same folder, which means the
files in them are permanently marked as modified and staged, since their
contents differ between the two folders.
This makes using the geoserver repo rather difficult.
I have been able to workaround the issue by marking the files as locally
ignored, which works fine as long as I stay on master, but means that I
can't switch to older branches that don't have these files (I get a warning
that the changes will get overwritten). This makes backporting commits
quite difficult.
So far, I have not been able to find a workaround for changing branches -
to do so I have to undo my local ignores, temporarily commit the
problematic files, then checkout the old branch and do whatever I need to
do there, then later reset the temporary commit when I return to the master
branch.
So, I have a couple questions:
1. Is anyone else having similar issues (I assume it is affecting all macOS
developers, I wonder if it also affects Windows developers). If so, have
you figured out any alternate workarounds?
2. Is it absolutely necessary to have two folders with effectively the same
name in the same directory? At the very least, is it possible to have them
in different directories?
Torben
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
