the only project I'm having trouble with is one tha lives a directory "lib", is there any naming restriction?

Hm, what is the issue specifically? Pants places no restrictions on what you name folders, other than avoiding some characters like

@

. What version of Pants are you using (

./pants --version

)? Likely this is an issue with source roots. See https://pants.readme.io/docs/source-roots

I'm using 1.29.0rc0 - I tried to change the

root_patterns

but no luck

Ah, good find! Indeed, Pants does use your top level gitignore to populate the option

pants_ignore

. You can turn this off by setting

pants_ignore_use_gitignore = false

in the

GLOBAL

section of pants.toml

thanks, that's very helpful 🙂

I’ll look on Monday at where this would be appropriate to add to the docs

Finding this thread just solved a confusing issue for my build, plus1 on the docs 🙂

Awesome! @salmon-television-63321 was your issue that a folder was being ignored that you didn’t expect?

Thanks @hundreds-father-404, my context was an upgrade from 1.18 to latest plus a switch to mixed mode builds. I have a jarfile from a jvm build being treated as a resource for a python build, which worked in 1.18 even with it .gitignore’d (maybe accidentally?) but fell off the wagon toward the end 🙂

Got it, that makes sense why that would stop working. Glad to hear you’re upgrading - let us know if we can help with anything else and if you have feedback or feature requests!

👌 thanks again, and the new docs look great!