Invalid symbolic links on the module source path
jonathan.gibbons at oracle.com
Sun Jul 19 16:57:15 UTC 2020
I see this conversation, but it sounds like there's no javac action
required at this point.
If there were to be action, it may be appropriate to have the file
manager ignore non-identifier file names by default.
On 7/19/20 2:52 AM, Florian Weimer wrote:
> * Andrew Dinn:
>> On 19/07/2020 09:01, Florian Weimer wrote:
>>> Emacs creates dangling symbolic links while source files are edited,
>>> as a form of lock file. These have names of the form ".#Main.java"
>>> (for a source file called Main.java). Should javac skip reading these
>>> non-source files, based on their name?
>>> Presently, javac attempts to open these files and reports an error,
>>> terminating the compilation.
>>> (I wonder if there is a reasonably straightforward way to work around
>>> this using a JavaFileManager.)
>> I actually like this behaviour because it stops me rebuilding whren I
>> have unsaved edits to JDK sources (n.b. the JVM build also fails if it
>> picks up one of these files via a wildcard substitution).
>> So ... it's not a bug it's a feature -- and quite a useful one as far as
>> I am concerned ;-)
> That's actually a good point. I was triggering rebuilds once .#*.java
> files popped up. Those rebuilds obviously fail all the time. Once I
> started ignore .#* files in the change detection logic, the experience
> is actually fairly pleasant.
More information about the compiler-dev