On the benefits of the Maven switch

One of the really cool things about Maven is how well-supported it is. Ironically, I realized this while trying to figure out how to solve a bug in Maven-Tycho.
Long story short: My build machine at home is running Windows and that is causing troubles with Tycho doing cross-platform builds on it.

For several reasons, switching the OS is not an option for me and so I went on looking for alternatives. I came across CloudBees, which — as their company name suggests — are offering a bunch of services in the cloud. Most notably, a free Jenkins instance.

The service works suprisingly well so far. And thanks to the power of Maven, setting it up was a breeze. A picture tells a thousand words 🙂

CloudBees Jenkins instance

Build infrastructure changes

First of all, sorry for the slow updates! I’ve been quite busy lately, and LogSaw already does pretty much all I need, so the pressure for me to make changes has been quite low. Though, it’s still all alive and development should continue soon 🙂

I have been playing around with Buckminster some more recently, and I ended up making the whole development process alot easier (did I already mention, that I really like Bucky?). So, if you ever wanted to play around with the LogSaw source yourself, but were unsure on how to get started: The new Building LogSaw tutorial should help you to get started.

Switch to Git SCM completed

I have just completed moving the source code to Git SCM. The master repository is now hosted on GitHub. However, a clone of it is also hosted on SourceForge because it doesn’t allow to point to an external Git repo only.

Then again, Git is very capable in terms of syncing multiple repos so this shouldn’t be much of an issue 🙂