OK, let me try to state this more clearly. Reporting plugins like checkstyle and pmd and javadoc look for the output of their corresponding build plugins. If they don't find it, they fork a build lifecycle to build it. They aren't especially protected against stale data.
I really can't fork build in this case, so I'll just fail. I'm not entirely thrilled with all of this, but it seems the best fit to the design of the site plugin's structure. On Wed, Mar 30, 2011 at 2:55 AM, Anders Hammar <and...@hammar.net> wrote: > To me this sounds very similar to what the surefire reporting plugin does. > Have a look at that code: > http://maven.apache.org/plugins/maven-surefire-report-plugin/ > > /Anders > > On Wed, Mar 30, 2011 at 01:20, Benson Margulies <bimargul...@gmail.com>wrote: > >> I want to create a report which presents some results from a build. >> There is no way to recreate the data in the reporting context; the >> report must come from the build proper. >> >> Is the thing to do here to make the build proper leave the data behind >> in, for example, an XML file in target, and the reporting plugin to >> fail if the file is not there? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
