Ralf Taugerbeck created MRESOURCES-266:
------------------------------------------

             Summary: Resources are not copied to 
${project.build.outputDirectory}
                 Key: MRESOURCES-266
                 URL: https://issues.apache.org/jira/browse/MRESOURCES-266
             Project: Maven Resources Plugin
          Issue Type: Bug
    Affects Versions: 3.2.0
         Environment: Maven 3.6.3, Java 11, macOS
            Reporter: Ralf Taugerbeck


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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to