RCS
Blog posts for the tag #RCS
05-Jul-2017
Visualise Git commits between two tags using Gource
Gource is an awesome tool. It creates stunning, elastic visualisations of your RCS activity. I've written about it in the past when I first tried to use it on OSX with Subversion. Now that things have moved on and I am using Git I decided to give Gource another go.
Gource is an awesome tool. It creates stunning, elastic visualisations of your RCS activity. I've written about it in the past when I first tried to use it on OSX with Subversion. Now that things have moved on and I am using Git I decided to give Gource another go.
16-Jun-2017
Multi module builds with Maven 3.5 and the parent-child pom version management
Back in 2015 I wrote about getting around Maven's parent-child project version dependency issue, that was with Maven 3.2.2. Now that Maven 3.5 has been released the same approach doesn't work so I had to rethink how to handle my submodule builds going forward.
Back in 2015 I wrote about getting around Maven's parent-child project version dependency issue, that was with Maven 3.2.2. Now that Maven 3.5 has been released the same approach doesn't work so I had to rethink how to handle my submodule builds going forward.
08-Nov-2015
Getting around Maven's parent-child project version dependency issue
I'm slowly coming around to liking Maven now. My first experience with it was less than nice, I put that down to not really understanding what it is and how to use it effectively. However one thing that has always bothered me with Maven was it's parent-child project version dependency. You have to specify the version in the parent pom.xml file, then for every child project (module) you have to reference that parent by its version. This is manageable if you only have a handful of child projects but once you get lots, changing your version number each release becomes a substantial task. I know there are plugins to manage this, but in my opinion this just complicates matters. Specifying the parent version as a property in one place would be so much easier.
I'm slowly coming around to liking Maven now. My first experience with it was less than nice, I put that down to not really understanding what it is and how to use it effectively. However one thing that has always bothered me with Maven was it's parent-child project version dependency. You have to specify the version in the parent pom.xml file, then for every child project (module) you have to reference that parent by its version. This is manageable if you only have a handful of child projects but once you get lots, changing your version number each release becomes a substantial task. I know there are plugins to manage this, but in my opinion this just complicates matters. Specifying the parent version as a property in one place would be so much easier.
10-Apr-2014
Playing around with Gource on OS X
A friend of mine showed me a video he made with Gource, so this got me interested in seeing how the two major repositories that I have been contributing for years now have evolved over time. So I decided to get this tool myself and give it a shot. It's amazing to see how a Subversion repository evolved over the life of a project and this is an awesome tool to help do just that.
A friend of mine showed me a video he made with Gource, so this got me interested in seeing how the two major repositories that I have been contributing for years now have evolved over time. So I decided to get this tool myself and give it a shot. It's amazing to see how a Subversion repository evolved over the life of a project and this is an awesome tool to help do just that.
Hi! You can search my blog here ⤵
NOTE: (2022) This Blog is no longer maintained and I will not be answering any emails or comments.
I am now focusing on Atari Gamer.
I am now focusing on Atari Gamer.