Uploaded image for project: 'Maven Shared Components'
  1. Maven Shared Components
  2. MSHARED-966

Resources are not copied to ${project.build.outputDirectory}

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Reopened
    • Major
    • Resolution: Unresolved
    • maven-filtering-3.2.0, maven-filtering-3.3.0
    • None
    • maven-filtering
    • None
    • Maven 3.6.3, Java 11, macOS

    Description

      Hi,

      after upgrading from 3.1.0 to 3.2.0 I get this weird issue. My build fails with a java.nio.file.NoSuchFileException for a file, that actually exists in the resources directory.

      What's special about the file is that it was extracted from a dependency artifact. I know this is a strange use case, but for us it is the only way to supply a common Velocity macro library file to other modules for Velocity template development with IntelliJ (only relative paths supported).

      File content and encoding do not seem to have an impact. Could it be because of an archive flag? If I modify and save the file, the build works fine again...

      If necessary, I can provide a stack trace or detailed log.

      Attachments

        1. maven-example.tgz
          1 kB
          Ralf Taugerbeck
        2. maven.log
          117 kB
          Ralf Taugerbeck

        Issue Links

          Activity

            People

              Unassigned Unassigned
              Lomacs Ralf Taugerbeck
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: