Java201.com

• Small Steps Lead to Big Improvements in Java Code Quality by Steven Hale   - [Clicks: 4]
  Instead of setting arbitrary targets to achieve better quality Java code, use an iterative improvement strategy that delivers visible, measurable results.
  http://www.devx.com/Java/Article/36231 - Dec, 2007
• Automation for the people: Continuous Integration anti-patterns by Paul Duvall   - [Clicks: 13]
  While Continuous Integration (CI) can be extremely effective at reducing risks on a project, it requires a greater emphasis on your day-to-day activities related to coding. In this installment of Automation for the people , automation expert and co-author of Continuous Integration: Improving Software Quality and Reducing Risk , Paul Duvall, lays out a series of CI anti-patterns, and more importantly, shows how to avoid them.
  http://www.ibm.com/developerworks/java/library/j-ap11297/index.html - Dec, 2007
• Automation for the people: Build Java projects with Raven by Paul Duvall   - [Clicks: 4]
  Ant is arguably the de facto build tool for the Java platform; however, other build tools, which support a more expressive paradigm that XML lacks, are entering the scene. In this installment of Automation for the people, automation expert Paul Duvall describes how Raven, a build platform built on top of Ruby, leverages the power of a full-featured programming language with the simplicity of a build-centric Domain Specific Language.
  http://www.ibm.com/developerworks/java/library/j-ap11067/index.html - Nov, 2007
• Automation for the people: Asserting architectural soundness by Paul Duvall   - [Clicks: 4]
  Is your software architecture what you think it is? The designs we communicate to each other aren't always what we expect when it comes to source code. Paul Duvall returns from his hiatus in this installment of Automation for the people to demonstrate how you can discover architectural deviations by writing tests using JUnit, JDepend, and Ant to discover problems proactively instead of long after the fact.
  http://www.ibm.com/developerworks/java/library/j-ap07107/index.html - Jul, 2007
• Introducing continuous integration by Paul Duvall, Steve Matyas, Andrew Glover   - [Clicks: 21]
  How continuous is your integration and what could your team be doing to improve it? A JavaWorld excerpt from Continuous Integration: Improving Software Quality and Reducing Risk (Addison Wesley Professional, June 2007)
  http://www.javaworld.com/javaworld/jw-06-2007/jw-06-awci.html - Jun, 2007

[Top]

• Spot defects early with Continuous Integration by Andrew Glover   - [Clicks: 10]
  Continuous Integration (or CI) is a process that consists of continuously compiling, testing, inspecting, and deploying source code. In many Continuous Integration environments, this means running a new build anytime code within a source code management repository changes. The benefit of CI is simple: assembling software often greatly increases the likelihood that you will spot defects early, when they still are relatively manageable. In this tutorial, a companion to his series In pursuit of code quality, Andrew Glover introduces the fundamental aspects of Continuous Integration and steps you through how to set up a CI process using best-of-breed open source technologies.
  [Formats: html, pdf]
  http://www.ibm.com/developerworks/edu/j-dw-java-cq11207-i.html - Nov, 2007

[Top]