Home › Blogs › Christoph C. Cemper's blog
Quality & Testing

Top 15 Ant Best Practices

<< CVS Reporting and Statistics Tools | DBunit - unit testing database bound code with Junit >>
Sat, 12/20/2003 - 00:44 — Christoph C. Cemper

Before Ant, building and deploying Java applications required a hodgepodge of platform-specific scripts, makefiles, proprietary IDEs, or manual processes. Now, nearly every open source Java project uses Ant. A great number of companies use Ant for internal projects as well – just like we use it even for non-java projects. The widespread use of Ant in these projects has naturally led to an increased need for a set of well-established best practices…

Top 15 Ant Best Practices by Eric M. Burke sounds interesting.

Average rating
 
 
 
 
 
(0 votes)

Comments

Fri, 01/09/2004 - 00:04 — bob (not verified)

Top 15 Ant Best Practices

hodgepodge???

wtf??

ok....

Similar entries

  • User Authentication and Authorization - Java vs. .NET Security, Part 4

    ONJava.com has the next part 4 of "Java vs. .NET Security" for User Authentication and Authorization up. The article compares the issues and techniques you can utilize in the respective technology. I like this article series….

  • Best Practice for Software Development Projects

    Skilled people, leading edge tech and spiral-model for succesful projects

  • Java vs. .NET Security

    Denis Piliptchouk provides a side-by-side technical comparison of security features of Java v1.4.2/J2EE v1.4 (beta2) and .NET v1.1 platforms in ONJava.com: Java vs. .NET Security, Part 1 – the first part considers Security Configuration and Code Containment – Cryptography and…

  • Regular Expressions in standard Java

    Regular Expressions in Java

  • Aspect-Oriented Programming (AOP) a paradigm introduction

    Aspect-oriented programming (AOP) is an exciting new paradigm that should have the same effect on software development that object-oriented programming (OOP) had 15-20 years ago. AOP and OOP are not competing technologies, but actually complement each other quite nicely. OOP is great for modeling common behavior on a hierarchy of objects. Its weakness is in applying common behavior that spans multiple non-related object models; this is where AOP comes in.