Then what I would do is list those reports you care about in the reports
section of the project.xml. Some of those reports may require that the
code gets compiled first. If you can't do the compile with maven, then
you won't be able to include those reports.
I reduced my reports section to:
<reports>
<report>maven-javadoc-plugin</report>
<report>maven-checkstyle-plugin</report>
<report>maven-changelog-plugin</report>
<report>maven-developer-activity-plugin</report>
<report>maven-file-activity-plugin</report>
<report>maven-tasklist-plugin</report>
<report>maven-linkcheck-plugin</report>
</reports>
then ran maven site and it never even tried to run java:compile.
-----Original Message-----
From: Reid Pinchback [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 21, 2005 8:21 AM
To: Maven Users List; Jamie Bisotti
Subject: Re: Alternate build step
Trying to coordinate work between local developers and an outsource
firm. All the info that "site"
publishes is exactly what I want. All the project and team info, link
to issues site, mailing lists, etc. is spot on. The only challenge is
to gradually get more out of the report generation while still using Ant
for the real guts of code building. Perhaps someday the entire build
will be Maven-based, but not yet. For now, I'm just tackling things one
step at a time until other developers have a chance to get used to Maven
being part of the environment.
--- Jamie Bisotti <[EMAIL PROTECTED]> wrote:
> What exactly do you want the "site" to consist of? Why not just do
> "maven checkstyle xdoc"?
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
