Skip to main content

Source control, change tracking, and regular builds

Posted by daniel on February 13, 2004 at 4:42 AM PST

Michael Ivey writes that if you don't yet use source control, change tracking, and regular builds in your process, you should implement them today.

For him, the most important to implement is change tracking. His What I want to know about your process is the latest java.net featured article . In it he writes, " Source control can be added to your development routine in a single day and for no money, assuming that company bureaucracy doesn't get in the way." The benefit is that "Source control gives you the freedom to undertake major refactoring projects or experiment with a potentially risky code change with a safety net. Just think of it as multilevel 'undo' for your source code."

As for the second practice, he writes "The first step to implementing regular builds is to find all of the files needed for a build and make sure that they are under source control. Then automate all of the manual steps with a build tool like make or Ant. The goal here is one command to a shippable build. There should not be any manual steps required to finish a build, because manual steps are opportunities for error."

Finally, he advocates a bug tracking or change tracking system and reminds you that there is a difference between priority and severity for change requests and that your tool should be able to handle both. He recommends Bugzilla as a free and open choice. In any event, use the article's trackback to chime in on the issues that Michael raises.


In
Also in Java Today
, If you would like to keep up with the latest RSS feeds from your favorite Java web sites and bloggers but would rather use your browser than a newsreader, take a look at Java RSS . In addition to java.net, you'll find feeds from The ServerSide, ONJava, The JavaLobby, java.sun.com, IBM's developerWorks, devX, and others.

Alexander and Olexiy Prohorenko introduce you to Using JUnit with Eclipse IDE. They take you through an introductory example and focus on developer tests. These are the tests that XP developers often refer to as Unit tests. The Prohorenkos point out that in the testing world, Unit testing already has a specific and different meaning.


In Projects and Communities The Java Desktop community homepage now features a tip of the week. In the first one, Mark Davidson points to java.net resources on writing unit tests.

The Java Communications homepage links to the latest relevant JSRs: SIP for J2ME (final), JAIN IM and Presence, and SAMS messaging.


In today's Weblogs Chris Adamson asks whether Java applications should look like native apps or should they advertise themselves as Java? In As Your Users Like It , Chris Adamson points to a problem for those people who advocate making Java applications run so smoothly, so much like a native application, that folks don't realize they are using Java. When I was done laughing at the following paragraph, I realized that Chris has outlined a real challenge that can't really be solved by a "Java Inside" campaign.

This is the paradox: if we do a great job of concealing the Java-ness of an application, then we don't really advance the platform (if that's even an important goal... should it be?). But it's a blunt reality that in the here and now, there are users who absolutely will not use a cross-platform look-and-feel application. Heck, I haven't worked anywhere where the management thought the Windows L&F was Windows-y enough (and I'm like, "what, our app is ugly and confusing... how much more like Windows do you want?"). Don't get me started on the Mac zealots. And as much as the multi-device argument makes sense in theory, in practice there are only three J2SE environments that matter (Windows, Linux, and Mac OS X), and it's a rare user that uses more than one.


In today's java.net News Headlines
:

Registered users can submit news items for the href="http://today.java.net/today/news/">java.net News Page using
our news submission
form
. All submissions go through an editorial review by news director
Steve Mallet before being posted to the site. You can also subscribe to
thejava.net
News RSS feed
.


Current and upcoming
Java Events
:

Registered users can submit event listings for the href="http://www.java.net/events">java.net Events Page using our href="http://today.java.net/cs/user/create/e"> events submission
form. All submissions go through an editorial review before being
posted to the site.


Archives and Subscriptions: This blog is delivered weekdays as the
Java
Today RSS feed
. All java.net members can subscribe to the email
updates for the site at the href="https://java-net.dev.java.net/servlets/ProjectMailingListList">
java-net Mailing Lists page. You must be logged in to subscribe
to
the javanet_Daily and javanet_Weekly lists. Also, once this page
is no longer featured as the front page of
java.net
it will be archived along with other past issues in the href="http://today.java.net/today/archive/">java.net Archive.