agilesWissen

What is the best way to communicate source code changes? Write a mail, send an instant message or hope the next cvs sync will inform all your co-worker? Vincent Massol suggests two solutions: “Diff emails on SCM commit” and “RSS feeds”. This solutions are good ideas for small projects, but with a lots of changes (important and unimportant) this doesn’t work.

I think the best way to communicate important source code changes is a project team Wiki with the ability to create source code links. This links should have two possible targets. When you click on a source code link in a standard browser, you will directed to the source code in a WebCVS view and a click in the Eclipse embedded web browser will open the source code.

If you use SnipSnap as project wiki tool, you can install my IDE Wiki Plugin for Eclipse to use source code links:

Links

• IDE Wiki Plugin – Project Site
• Screencast
• Installation Instruction
• Download (ZIP: plugin + SnipSnap extension)
• Eclipse Update Site (plugin only):
  http://ide-wiki.googlecode.com/svn/trunk/IdeWikiUpdateSite/

Findbugs looks for bugs in Java programs
Update-Site: http://findbugs.cs.umd.edu/eclipse/

PMD scans Java source code and looks for potential problems
Update-Site: http://pmd.sourceforge.net/eclipse

Checkstyle helps you ensure that your Java code adheres to a set of coding standards
Update-Site: http://eclipse-cs.sourceforge.net/update/

Code Analysis Plugin (CAP) checks dependencies between the classes and packages and gives you a hint about the architecture, reusability and maintainability.
Update-Site: http://cap.xore.de/update

moreUnit is a eclipse plugin that should assist you writing more unit test.
Update-Site: http://moreunit.sourceforge.net/org.moreunit.updatesite/

EclEmma is a free Java code coverage tool for Eclipse.
Update-Site: http://update.eclemma.org/

JAutodoc is an Plugin for automatic adding Javadoc and file headers to your source code.
Update-Site: http://jautodoc.sourceforge.net/update/

Das MathEclipse Projekt hat eine neue Version von der Java Wikipedia API veröffentlicht. Die API ermöglicht das Rendern von Wikipedia-Texten zu HTML, PDF und Docbook. Verwendung findet die API z.B. im “Eclipse Wikipedia Editor“.

Links

• Java Wikipedia API Projekt-Seite (License: Eclipse Public License – v 1.0)
• ChangeLog? – gibt’s leider nicht
• Wikipedia Markup
• Alternative Java™ API für SnipSnap Wiki Texte: Radeox

Google Video Link: CIJUG Emma vs. Cobertura (Feb 2007) via CIJUG

EclEmma is a free Java code coverage tool for Eclipse, available under the Eclipse Public License. Internally it is based on the great EMMA Java code coverage tool, trying to adopt EMMA’s philosophy for the Eclipse workbench:

• Fast develop/test cycle: Launches from within the workbench like JUnit test runs can directly be analyzed for code coverage.
• Rich coverage analysis: Coverage results are immediately summarized and highlighted in the Java source code editors.
• Non-invasive: EclEmma does not require modifying your projects or performing any other setup.

..implemented by Marc R. Hoffmann. It’s simply the best JUnit coverage plugin for Eclipse.

• Project Site
• Update Site: http://update.eclemma.org/

Wer schon immer mal wissen wollte wie viel Zeit (statistisch gesehen) in ein OpenSource Projekt (z.B. Firefox oder Eclipse) investiert wurde und was für Leute den Code geschrieben haben, der sollte sich Ohloh ansehen.

So ist es beispielsweise beeindruckend zusehen, das Eclipse 3.3 Europa, laut der Zusammenstellung von Ian Skerrett mit Hilfe von Ohloh, folgende Zahlen aufweist:

• 17 million LOC,
• 290 contributors,
• 5055 person years of effort, and
• $278,041,377 estimated cost of development.

Dozer is a powerful, yet simple Java Bean to Java Bean mapper that recursively copies data from one object to another. Typically, these Java Beans will be of different complex types. Dozer supports simple property mapping, complex type mapping, bi-directional mapping, implicit-explicit mapping, as well as recursive mapping. This includes mapping collection attributes that also need mapping at the element level.

• http://dozer.sourceforge.net/
• release notes

“The aim of Behaviour Driven Development (BDD) is to address this shortcoming and, by using terminology focused on the behavioural aspects of the system rather than testing, attempt to help direct developers towards a focus on the real value to be found in TDD at its most successful, or BDD as we call it.” — behaviour-driven.org

Links

• RSpec is a framework for practicing Behaviour Driven Development (BDD) in Ruby
• http://behaviour-driven.org
• A New Look at Test Driven Development
• “Beyond Test Driven Development: Behaviour Driven Development” – Google TechTalks March 17, 2006

Google TechTalks July 6, 2006

William Pugh

ABSTRACT I’ll talk about some of my experience in using and expanding static analysis tools for defect detection. The FindBugs tool developed at the Univ. of Maryland is now being widely used, including inside Google.

I’ll give an overview of FindBugs, show some of the kinds of errors we routinely find in production code, discuss the methodology we use for enhancing and expanding FindBugs and some of the recent additions to it, discuss ways of incorporating FindBugs into your development process (such as being able to get a report of all the warnings introduced since the last release of your software), and talk about the future of static analysis, including things such as a new Java JSR to provide standard annotations for things such as @NonNull and @Tainted. – (Google Video)

…is online now.

Links

• www.krugle.com
• Developers Get Their Own Mini-Google Search Tool
• wired.com: Here Comes a Google for Coders

Einen wirklich interessanten “Tips and Tricks” Artikel hat Riyad Kalla auf EclipseZone veröffentlicht. Er beschreibt wie man den internen Tomcat von Eclipse, der z.B. für die Eclipse Help-Pages verwendet wird, für eigenen WebApps nutzen kann.

• Article: Use Embedded Tomcat in Eclipse for a Webapp (Riyad Kalla)
• Demo: Eclipse Help Url (http://127.0.0.1:58581/help/index.jsp)

A short list of interesting podcasts about software and web development:

• Agile Toolkit Podcast – Agile Developement Conversations
• Tonabnehmer – Audiokolumne zur agilen Softwareentwicklung
• Zdot – Java podcast
• The Java Posse (Java News and Interviews)
• IT Conversations
• Software As She’s Developed
• QA Podcast – Conversations about Software Quality Assurance
• WebSphere Technical Podcast series
• WebDevRadio
• WebDevDesign – 21st century Web Design & Development Podcast
• Web Essentials 2005
• Web 2.0 Show – podcast about the “new” web

In der iX 10/2005 gab’s einen mehr oder weniger interessanten Artikel mit einigen Erkenntnissen:

Der Servlet-Zugriff erfolgte in Vorversuchen in einer Variante direkt über Tomcat, in einer anderen über das Apache-Modul mod_jk. Letzteres stellte sich als rund 30 Prozent langsamer heraus, …
…
Im Vergleich zum statischen Zugriff auf das 1000-Zeilen-Dokument benötigt die JSP/JSTL Lösung rund 30-mal so lange.
…
Mit der Velocity gab es zudem generell Probleme bezüglich Stabilität bei hoher Last.
…
Der Test hat aber deutlich gezeigt, dass sich die Java-Lösungen durchaus sehen lassen können. Sie sind nicht nur performanter als das in [1] mit 39 beziehungsweise 20 Prozent gemessene Perl, das aus anderen Gründen für das Projekt nicht in Betracht kam, sondern auch schneller als FastCGI.

iX Artikel 10/2005 S.124: Auslieferungsmethoden im Performancevergleich

Is this the result of a heavy distributed programming team?

>>Answer< <