You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
symlinks are being resolved into absolute path, MASSEMBLY-965 #89
Checkout https://github.com/wilx/MASSEMBLY-965. It has symlink in the resources directory. The project shows the ls -l of the link and then shows the tar tvf of the resulting TAR file. The TAR file contains the absolute path for the symlink instead of the relative path that is in the source:
Activity
plamentotev commentedon Sep 17, 2022
@wilx thanks for reporting. Do you have test/example project that reproduces it? We have symlink test so I wonder why it didn't caught the issue.
wilx commentedon Sep 17, 2022
Checkout https://github.com/wilx/MASSEMBLY-965. It has symlink in the
resourcesdirectory. The project shows thels -lof the link and then shows thetar tvfof the resulting TAR file. The TAR file contains the absolute path for the symlink instead of the relative path that is in the source:wilx commentedon Sep 17, 2022
As for the test, it only checks that the symlink reaches the target. That is true. But the value of the symlink is not checked.
Fix link destination, fixes codehaus-plexus#89
gnodet commentedon Sep 19, 2022
Here's the output of the MASSEMBLY-965 build with the above PR:
wilx commentedon Feb 24, 2023
Ping.
Fix link destination, fixes codehaus-plexus#89