Yes, will go down this route.
Fun side note: that warning was so far mostly applied to the outputDirectory
part. But this is just the path INSIDE the zip. So most of the warnings have
been pretty much useless ;)
Will continue to work on this. Probably we might also extract the path handling
o
I'd prefer to switch to Path, and in this case use Path.resolve
You should add that to the test.
I agree that a path starting with "/" should be interpreted as an absolute
path, and AFAIK the warning is there already for ages so I don't mind changing
the behavior.
thanks,
Robert
On 1-1-2020 23:2
Hi lords and ladies!
I try to get my head around the ticket MASSEMBLY-775.
It is related to MASSEMBLY-746 and MASSEMBLY-665.
The problem is basically that a reference to /somedirectory is
interpreted as absolute path on *nix and as relative path on Win*.
And sometimes we have code of the form
