Quelea is by far the "side project" that takes up the majority of my time. To aid with testing, I built in CI relatively early with a Jenkins server running on a custom VM. This was great - I could just push a change to the repo from anywhere, and then point the user to the CI release. They'd download it and be able to confirm whether the fix had worked (or not!) I've since switched to Travis and retired said VM (it's one less thing to maintain, and now everything is on Github.) But both these setups had one main issue - the windows installer wouldn't get built as part of this process, since they were Linux boxes and innosetup doesn't have a linux distribution. Travis has added windows support, but it's in early release, and in any case I'd like the entire build process to be able to run on any Linux box - it makes it both quicker and more transferrable if we ever need to move elsewhere. I therefore looked into using wine in the CI release to
By far the most popular post on here (shock, I know!) was to do with using the Dropbox Java API from a desktop Java app . At the initial time of writing, this wasn't really documented, so the OAuth flow in particular required a bit of guesswork to get it going. I haven't done any work with this API in quite a number of years now, and it appears the original v1 API was switched off a few months back, so that example will no longer work. This API has much better documentation than the v1 API did back in 2012, and if you're doing any serious work with it then looking through the SDK and the SDK examples on Github is a must. That being said, for completeness I thought I'd provide an equivalent code snippet for the v2 API. You'll need the appropriate Maven or Gradle dependency: <dependency> <groupid>com.dropbox.core</groupid> <artifactid>dropbox-core-sdk</artifactid> <version>3.0.5</version> </dependency&g