# development


08/30/2016, 8:16 PM
in v1 engine, if bundle fileset is literal path, then it is not converted to LazyFilesetWithSpec, and during bundle_create, if the path does not exist, error will be raised. if bundle fileset is globs and it does not match any files, pants runs fine. in v2 engine, since fileset is converted to EagerFilesetWithSpec in all cases, no error will be raised even if a non-exist literal path is given. I try to unify these cases. What I want to do is for a given fileset (either literal path or globs), if it matches no files, we don’t raise an error, but instead print a warning telling user that fileset matches nothing. what do you think?