Uploaded image for project: 'Maven Compiler Plugin'
  1. Maven Compiler Plugin
  2. MCOMPILER-174

Maven compiler plugin <excludes> doesn't work all the time

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Auto Closed
    • Affects Version/s: 2.4, 2.5
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      N/A

      Description

      When you set a source file as

        <configuration>
          <excludes>
            <exclude>com/you/example.java</exclude>
          </excludes>
        </configuration>

      it doesn't pass the file in with the list of .java files to javac. However, it still passes in the ./src/ directory under the -sourcepath option to the javac command. Thus, javac still knows that the file exists and can try to compile it anyways under certain circumstances.

      The passing of ./src/ under -sourcepath is redundant anyways, as every single file to be compiled is passed (in my case, all 391 source files) to javac. The only possible result from passing ./src/ (or at least the only one I can think of) is that a file which is in your ./src/ directory yet excluded by the maven-compiler-plugin can still be seen (and compiled) by javac. This can cause inexplicable results and a lot of confusion since it operates in a counter-intuitive way.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              matt5784 Matthew Lavin
            • Votes:
              6 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: