This project needs a .jar that I can add to my workspace without having to import the whole project into eclipse!
I may very well add a jar file for people to download but I cannot guarantee that it's always up to date. Creating a new jar file for every commit adds quite some overhead. Would that be acceptable?
That's fine - but does git overhead really matter that much? It's not like GitHub has any space limits, and git checkout is pretty damn fast anyway. shrug Either way is fine though - I'd just commit the Jar though, because otherwise I'd end up having to keep the Jar on the download page up to date because I'm OCD like that.
I didn't mean overhead as in space but as in time (exporting jar file from eclipse, uploading to github).
Ah, I see. In that case just write the ant script and add instructions to 'ant jar' in the README, maybe?
Adding build.xml to support building jar files from source. Solves #15.
Signed-off-by: Patrik Åkerfeldt <email@example.com>
Try it out!