Well, that's not how the action-specific validation file work. I don't know of any trivial workaround. IMO it doesn't make much sense to throw them into a single directory--the idea is to keep related functionality *together*, and since the validation files are tied closely to the action they validate, they're in the "right" spot.
Some build environments (like
Maven) would have a separate directory for non-Java files, but even then they'd still be in the required package hierarchy.