I believe this is related to a bug in maven-filtering or maven-resources- plugin. According to
https://issues.apache.org/jira/browse/MRESOURCES-237 the behavior how symlinks are handled has changed between version 2.7 and 3.0.x of maven-resources-plugin. This is apparently fixed in maven-filtering 3.3.0. I don't know why we see this problem only now because the bug has been reported four years ago. I have pushed a new upstream version of maven-filtering to the experimental branch but I have not uploaded it yet. The upgrade would break Maven with "No implementation ... was bound" error and I presume some extra steps have to be taken in order to match this package with our Maven version.
signature.asc
Description: This is a digitally signed message part
__ This is the maintainer address of Debian's Java team <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.
