Hi Philippe,
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: lundi 24 janvier 2005 03:51
> To: [EMAIL PROTECTED]
> Subject: [jira] Commented: (MPDASHBOARD-9) Link aggregator results with
> full reports
>
> The following comment has been added to this issue:
>
> Author: pkernevez
> Created: Sun, 23 Jan 2005 9:49 PM
> Body:
> I'm surprised that you had to make some changes, I expected that it was to
> many work (I use it on real projects without any trouble).
More specifically I've had to change the following:
- modify subproject1/maven.xml to copy the changelog-report + file-activity
XML files to ${maven.gen.docs} insteqd of ${maven.build.dir}. Otherwise they
are not processed by the site goal and the asserts in the top level
maven.xml fail. I've also modified the pregoal to be on site rather than on
dashboard.
- modify the clover asserts in the top level maven.xml (the one you had
commented out were not correct).
Note: I've just found a bug in plugin-test: the clean was not performed
properly on the master project and I think that's probably what caused the
first problem mentioned above. I've also now cleanly separated the shared
build files from the master project. This removes the generation of the
dashboard report for subproject2. I'll check all of this when I get internet
connectivity.
>
> That's normal that links are only generated for the first project (and
> this is tested : cf the comment
> <!-- The project2 don't have any report we check that there isn't any link
> --> in the maven.xml that test the plugin ;-)
>
> The reasons are:
> - The project2 : has only XML report, so the dashbord has information
> about the number of errors, bit we don't have any html report to make
> links.
> - The project3 : hasn't any XML or Html report, so there isn't any link.
Ok, I've just understood!
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
