the corner office : tech blog

I've always left the mvn release:blah tomfoolery to colleagues. I've been fiddling with some projects at home and even though it's not strictly necessary for pet projects, I've been trying to release fixed versions of some of them.

If I have dependencies on other libraries from the project, I usually show the version tag as ${parent.version}. The maven-release plugin didn't like that, dying with an error:

The version could not be updated: ${parent.version}

The solution (found somewhere online) is to use ${pom.version} instead of ${parent.version}. Maybe it's even more correct to handle libraries via the parent pom's dependencyManagement element, but ${pom.version} works for me.