Ant, Ivy, JUnit 4.8.2 and OpenPojo – Part 1: Challenges

July 6th, 2010

Just Do It!

Just Do It!

After announcing my plans to compare Ant, Maven and Gradle implementations in my previous post Ant, Maven, Gradle…or something else… almost 2 months ago, I have finally found some time to begin my little experiment.

The initial implementation involves the use of Ant with Ivy, to build and test a simple Java class. Dependencies including Ivy itself, JUnit 4.8.2 and OpenPojo should be obtained as part of the build itself. Anyone wishing to use the build should only require a working Java environment and Ant installed. It appeared to be simple enough in principle. It turns out to be a little more complicated in practice.

Continue reading “Ant, Ivy, JUnit 4.8.2 and OpenPojo – Part 1: Challenges” »

Share and Enjoy:
  • Print
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • DZone
  • RSS
  • Slashdot
  • StumbleUpon
  • Technorati
  • Twitter
  • Add to favorites

Ant, Maven, Gradle…or something else…

May 2nd, 2010

Arrested for not using a build tool!!

Arrested for not using a build tool!!

Do you use a build framework? Which build framework do you use? Is your build framework open-source, commercial or even custom? Ant, Maven and Gradle are three open-source build frameworks that I plan to use in a build experiment.

The experiment is intended to be the first of many set around the build process. Future planned experiments include the integration of these frameworks with repository managers, continuous build integration, static code analysis/error detection and reporting capabilities to determine technical debt.

Continue reading “Ant, Maven, Gradle…or something else…” »

Share and Enjoy:
  • Print
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • DZone
  • RSS
  • Slashdot
  • StumbleUpon
  • Technorati
  • Twitter
  • Add to favorites

JUnit 4 Test Logging Tips using SLF4J

February 26th, 2010

SLF4J LogoWhen writing JUnit tests developers often add log statements that can help provide information on test failures. During the initial attempt to find a failure a simple System.out.println() statement is usually the first resort of most developers.

Replacing these System.out.println() statements with log statements is the first improvement on this technique. Using SLF4J (Simple Logging Facade for Java) provides some neat improvements using parameterized messages. Combining SLF4J with JUnit 4 rule implementations can provide more efficient test class logging techniques.

Continue reading “JUnit 4 Test Logging Tips using SLF4J” »

Share and Enjoy:
  • Print
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • DZone
  • RSS
  • Slashdot
  • StumbleUpon
  • Technorati
  • Twitter
  • Add to favorites