On Mon, 16 Dec 2002 [EMAIL PROTECTED] wrote:
> >> What/where do you see a large overlap with CC?
>
> I guess more of an overlap of intention:
> The scheduling aspect of CC is covered by Quartz plugin for Jelly (ok, I
> guess that is not maven per se)
> The maven reactor covers ant build and super-builds.
> Unit Test reporting
> And the fact that others were integrating email reporting etc into the
> reactor.
>
> >> Other than that there have been some efforts by users to have CC just
> call
> >> out to maven as its builder instead of ant.
> Is this perhaps the answer?
> Or will this result in duplication of information?
>
> Currently, the POM knows just about everything there is to know about the
> project. Some of this (e.g. SCM details) would be duplicated in the CC
> config.
Yea, I think a maven builder for cruise control would be nice. At the
very least, CC could use the maven generated ant files.
The reporting in maven is sort of different than what I would exepect from
a CI tool. The CI tool needs just to tell me that something broke and
what it was, and when the build was sucessful. Maven gen'd docs are great
for project docs and communication. Something that may be generated at
each build perhaps, or every X builds or something.
--
=====================================================================
Jeffrey D. Brekke [EMAIL PROTECTED]
Wisconsin, USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
