[MASSEMBLY-965] Symbolic links get copied with absolute path

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.6.0
• Assignee: Slawomir Jaranowski
• Reporter: Marc Guillemot
• Created: 05/Jul/22 14:36
• Updated: 09/May/23 19:37
• Resolved: 01/May/23 22:27

Description

Copied symbolic links in a `<fileset>` have an absolute path as target and not the one of the original resource.

Example:

Source: foo -> ../my-file1

Assembly: foo ->/home/marc/projects/demo/src/somestuff/myfile1

This is a regression compared to 3.3.0. According to git bisect, the problem has been introduced with commit

https://github.com/apache/maven-assembly-plugin/commit/937750250bfe06333f92351fa1a19a9cd5e59d28

Pull Request with failing integration test follows.

Issue Links

• is depended upon by: MPOM-396 upgrade Maven Assembly Plugin to 3.6.0
• is duplicated by: MASSEMBLY-971 Symbolic links created by the plugin are absolute (i.e., the build environment is leaking through them)
• relates to: MSHARED-1252 Bump plexus-io to 3.4.1 for maven-assembly-plugin
• links to: GitHub Pull Request #82
• links to: GitHub Pull Request #121
• links to: Plexus-IO issue #89