[ https://issues.apache.org/jira/browse/MSHARED-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460639#comment-17460639 ]
Jimisola Laursen edited comment on MSHARED-966 at 12/16/21, 11:49 AM: ---------------------------------------------------------------------- [~G-Tsak] I concur. We have to use mvn clean everywhere now as a workaround. was (Author: JIRAUSER281352): [~G-Tsak] I concur. We had to change our entire pipeline to use mvn clean otherwise maven will fail. > Resources are not copied to ${project.build.outputDirectory} > ------------------------------------------------------------ > > Key: MSHARED-966 > URL: https://issues.apache.org/jira/browse/MSHARED-966 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-filtering > Affects Versions: maven-filtering-3.2.0 > Environment: Maven 3.6.3, Java 11, macOS > Reporter: Ralf Taugerbeck > Assignee: Sylwester Lachiewicz > Priority: Major > Fix For: maven-filtering-3.3.0 > > Attachments: maven-example.tgz, maven.log > > > 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.20.1#820001)