The docs directories contain binary files in various graphic formats: svg,
png, gif, jpg and the like.
I haven't made a practice of checking in the 'sources' for these, because
they're nearly always created with proprietary tools, such as Visio or
OmniGraffle. The workflow for graphics is different
Well, here’s a rule of thumb: if the file was generated by a compiler it’s
probably not source :-)
Binary files such as images, diskstores, stats, etc should ok. There are lots
of discussions on this topic, see [1] for example. Take a look at our current
list of rat excludes in ‘gradle/rat.g
I don't know about apache policy, but I think anything that can't be easily
modified is probably a bad thing to have in the source code. If there is a
binary jar, but there's no way to update the jar to modify the test that
seems like a problem.
Since we have a framework to run tests with old vers
[bump]
I want to see a definitive reference on what's allowed to be in the src of
an Apache project before we take actions to change any tests that use
binary resources.
We have unit tests and regression tests that are using binaries (including
stat files, diskstore files, class files). Jumping t
