deployment fails when functionCode path begins with "../"

[refacktor]

In some complex projects with modules, it is sometimes more efficient to reference the code in a relative path that begins with "../". This currently fails with an error about invalid S3 path. As a workaround you can use ${project.basedir}/../ but this is not obvious to many non-experts in Maven.

[SeanRoy]

Thanks, I'll have a look.