Browsing All posts tagged under »maven«

Build Scripts and External Dependencies

February 15, 2013


I recently ran across some project code that when checked out of version control, failed with an obscure warning.  After some digging around in the code, I realized the script made a reference to an external plugin library.  I had no clue where to acquire this library or setup this build.  I had to reach […]

Dependency Management in .NET

December 17, 2011


I have been a Java developer for over 10 years, during which I have used Maven or one of it’s successors (Gradle or Ant+Ivy) for build and dependency management.  It was obvious to me early on that Maven’s dependency management was its killer feature.  I began evangelizing Maven and converting teams to use it.  The days of […]

Thoughts on Application Lifecycle Management (ALM)

March 4, 2011


Last week, I was asked to give my opinion on Application Lifecycle Management or ALM.  Specifically, I was asked how can teams effectively manage their design, development, test and deploy processes as well as pick the right tools for the job.  Here is the answer I gave: The cornerstone of a strong ALM process is based […]

Maven Tip: Disabling Profiles when a Property Does Not Exist

February 9, 2011


I wanted to share a method for enabling a Maven Build Profile in the absense of a system property.  I did not see this approach documented in the current version of the Maven Build Profile documentation, so I thought I would share it. I find this approach particularly useful for turning off build features whenever […]

Build Once, Deploy Many

September 9, 2010


I have encountered more than one development team who takes the approach of building their application from source for every environment they plan on deploying to. While this approach works (and depending on the technology, may be necessary), it introduces numerous opportunities for errors and makes debugging a failed deployment increasingly difficult. By migrating to a Build Once, Deploy Many approach, your team can simplify their deployment process, by making it repeatable and easier to debug.

A Practical Approach to Unit Testing

May 7, 2010


Last year I was asked to give a 1 day workshop on how to write unit tests. I put together a presentation and workshop format and it was a huge success. The team quickly took to not only writing unit tests but was able to quickly utilize mock frameworks and other testing tools. Code coverage for the application quickly jumped and management was pleased. I recently took another look at this presentation to see if I wanted to revise anything and I thought that I might want to share some of the thoughts here. These guidelines are intended to get somebody started with unit testing quickly, but could be a welcome refresher for somebody who has been writing tests for a while.