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
Pants uses files with the magic prefix "BUILD". Sadly, some other build systems also use BUILD files.
Would Pants-team accept a patch to make this configurable, so that Pants can co-exist with other BUILD-using systems?
Based on a brief inspection, the pattern is consolidated to a few places, and I think it would be pretty straightforward to thread it through from the global pants.ini options.
The text was updated successfully, but these errors were encountered:
@nicks : It should be possible to accomplish this with existing options by suffixing all of pants BUILD files (ie, as BUILD.pants), and then setting the build-ignore option in pants.ini to something that will cause unsuffixed BUILD files to be ignored:
$ ./pants help-advanced | grep -A3 'build-ignore='
--build-ignore=<str> (--build-ignore=<str>) ..., --build-ignore="[<str>, <str>, ...]", --build-ignore="+[<str>, <str>, ...]" (@fromfile value supported) (default: ['.*','/dist/','bower_components','node_modules','*.egg-info'])
Paths to ignore when identifying BUILD files. This does not affect any other
filesystem operations. Patterns use the gitignore pattern syntax (https
://git-scm.com/docs/gitignore).
Pants uses files with the magic prefix "BUILD". Sadly, some other build systems also use BUILD files.
Would Pants-team accept a patch to make this configurable, so that Pants can co-exist with other BUILD-using systems?
Based on a brief inspection, the pattern is consolidated to a few places, and I think it would be pretty straightforward to thread it through from the global pants.ini options.
The text was updated successfully, but these errors were encountered: