[MSHARED-966] Resources are not copied to ${project.build.outputDirectory}

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: maven-filtering-3.2.0, maven-filtering-3.3.0
• Component/s: maven-filtering
• Environment: Maven 3.6.3, Java 11, macOS
• Assignee: Unassigned
• Reporter: Ralf Taugerbeck
• Created: 30/Aug/20 07:40
• Updated: 26/Feb/24 21:23

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.

Issue Links

• causes: MRESOURCES-278 Regression - Changed copy behaviour if file already exists
• is related to: MSHARED-1004 Two (2) issues with symbolic links