Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Subject: RE: [javacreport] Generating compilation reports
Date: Mon, 5 Apr 2004 09:07:52 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: 
 <1586DE6EBC0FF742BBC32EECA73847310D66E1@omnilogic05ma.OTMA.OMNILOGIC.ES>
content-class: urn:content-classes:message
Thread-Topic: [javacreport] Generating compilation reports
Thread-Index: AcQYhZT8g9uEb1FBQNuM/95GfdT5NQAabkqAAHrriDA=
From: "Roberto Juarez" <rjuarez@omnilogic.es>
To: "Ant Users List" <user@ant.apache.org>

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 [SMTP:scott.stirling@workscape.com]
> Enviado el:	viernes, 02 de abril de 2004 22:22
> Para:	Ant Users List
> Asunto:	RE: [javacreport] Generating compilation reports
>=20
> > From: Roberto Juarez [mailto:rjuarez@omnilogic.es]
> >=20
> > I believe most of us know about the <junitreport> task, which=20
> > is the counterpart of the <junit> task. I also believe that=20
> > we all know about the <javac> task, but, does anyone know=20
> > about a <javacreport> task? I think it would be great to have=20
> > such a tool for generating compilation reports,=20
>=20
> 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.
>=20
> > [e]specially in
> > multideveloper environments with people updloading code to a=20
> > centralized server for centralized compilation.
>=20
> 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.
>=20
> 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).
>=20
> 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.
> =
***********************************************************************
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org