I also like Dawid's idea to have a separate "big test data" repository somewhere...
+1 for some better separation here. Source release and svn checkouts are bloated because of
all this test data.
E.g. linefile data is over 5MB, snowball test data is over 3MB, ...
Maybe we should separate this out in svn? its "artifact" is a .jar file
with all these huge files in the appropriate places or something?
So basically we could sucker this thing down with ivy and put it in the classpath like
any other dependency.
The problems that make it hard though, are versioning and "releasing" this thing:
- if its outside of dev/ SVN that makes versioning the testdata wrt different releases/branches hard.
this could easily get annoying and complicated.
- where would we put the resulting "jar" to download via ivy? I dont think we should be downloading
this from SVN, since our source releases would actually have this as a test dependency.