[
https://issues.apache.org/jira/browse/MCOMPILER-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411750#comment-17411750
]
Robert Scholte commented on MCOMPILER-454:
------------------------------------------
The only issue I can think of is a bug in JDK8 on linux,
[JDK-8177809|https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8177809] that
removes the milliseconds from a timestamp, indicating the file hadn't changed.
IIRC [~martinkanters] and [~mthmulders] already worked on a fix for that.
> The compiler plugin does not always detect removed Java files
> -------------------------------------------------------------
>
> Key: MCOMPILER-454
> URL: https://issues.apache.org/jira/browse/MCOMPILER-454
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.8.1
> Reporter: Lorenzo Bettini
> Assignee: Robert Scholte
> Priority: Major
> Attachments: example.zip
>
>
> I'm doing some experiments with a very simple Maven project (see the
> attachment) where I set the maven-compiler-plugin to the latest version 3.8.1
> to see whether the compiler effectively detects the removal of a Java file
> and correctly recompiles the sources (and tests). In the project, there are
> two Java sources App.java and App2.java.
> I run `mvn test-compile`
> then I remove the App2.java file
> I run again `mvn test-compile`
> sometimes the removed Java file is detected and the sources and tests are
> recompiled (the old App2.class is also removed of course). Sometimes, this
> does not happen ("Nothing to compile - all classes are up to date").
> I'm afraid I don't understand when this works correctly and when it does not.
> But it consistently happens: sometimes the right behavior, sometimes the
> wrong one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
