Community
Participate
Working Groups
Configuration files (.lst files) have single-string entries for injars, sourceroots, classpath, bootclasspath, etc. that require platform-specific internal delimiters, which means the .lst files can't be reused across platforms. I recommend updating the path parsers to accept both the local platform delimiter or one of ';' or ',' as a delimiter for these paths.
This seems to be a non-issue at this point, since the VMs are happy with the default path separator.
Why is this invalid? Does ':' or ';' work on all platforms? The default varies with platform.
It has been a non-issue since I reported it way back. My sense was that ';' was starting to be like '/' and working on all the VMs, but I'm not certain. If anyone on another platform encounters a problem we can reopen it. But you're right, it shouldn't be marked as invalid.
Resolving as LATER until there is user feedback that this needs fixing.
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.