ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roberto Juarez" <>
Subject RE: [javacreport] Generating compilation reports
Date Mon, 05 Apr 2004 07:07:52 GMT
I think centralized compilation reports are good for all teams. This is why: without a report
you have no idea of whether the source code at the repository (CVS, SourceSafe, ...) compiles.

> -----Mensaje original-----
> De:	Stirling, Scott []
> Enviado el:	viernes, 02 de abril de 2004 22:22
> Para:	Ant Users List
> Asunto:	RE: [javacreport] Generating compilation reports
> > From: Roberto Juarez []
> > 
> > I believe most of us know about the <junitreport> task, which 
> > is the counterpart of the <junit> task. I also believe that 
> > we all know about the <javac> task, but, does anyone know 
> > about a <javacreport> task? I think it would be great to have 
> > such a tool for generating compilation reports, 
> But who would consume a compilation report and why?  The enduring value of a compilation
report is even less than that of a JUnit report.
> > [e]specially in
> > multideveloper environments with people updloading code to a 
> > centralized server for centralized compilation.
> I have visions of truckloads of source code statements, lined up and waiting to be dumped
into a giant chute, swirling, sucking loud machinery crunching it up and ejecting shiny blocks
of byte code at the other end.
> How do they do things where you work?  Don't developers rebase/update/resync their view/workspace
and then compile stuff locally before checking in/delivering?  I'm not criticizing your suggestion
so much as pushing for more details about the development process that would make such a report
valuable.  Just curious (plus it's Friday, so what the hell).
> Scott Stirling
> Workscape, Inc.
> ***********************************************************************
> This message is intended only for the use of the intended recipient and
> may contain information that is PRIVILEGED and/or CONFIDENTIAL.  If you
> are not the intended recipient, you are hereby notified that any use,
> dissemination, disclosure or copying of this communication is strictly
> prohibited.  If you have received this communication in error, please
> destroy all copies of this message and its attachments and notify us
> immediately.
> ***********************************************************************
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message