Ticket #2 (closed enhancement: fixed)

Opened 5 years ago

Last modified 3 years ago

Document changes in finding report

Reported by: mrumpf Owned by: amandel
Priority: major Milestone: unscheduled
Component: jCoderZ-report Version:
Keywords: Cc:

Description

We should have a section in the main CC screen for each build that documents the changes in the finding report, in comparison to the previous build.

Change History

Changed 5 years ago by mrumpf

  • owner changed from amandel to mrumpf

Changed 5 years ago by mrumpf

  • milestone changed from 1.0 to 1.1

Changed 5 years ago by amandel

The diff could be generated out of two jcreport files. And the output could be again xml which then could be used by a cruise control style sheet to generate HTML output.

From my feeling this should be placed on the main page above or below the top 10 violation list. Also limited to a maximum of 10 lines (starting with new violations and leaving out the fixed violations if no space is left)

Changed 5 years ago by anonymous

  • milestone changed from 1.1 to 1.2

Changed 4 years ago by mgriffel

  • milestone changed from 1.2 to 1.3

Changed 4 years ago by amandel

  • owner changed from mrumpf to dcoppola
  • milestone changed from 1.3 to unscheduled

Dino - you played around with the xml diff tool from Sun. Do you think this could be a way top start?

Changed 3 years ago by amandel

  • owner changed from dcoppola to amandel
  • status changed from new to assigned

Changed 3 years ago by amandel

  • status changed from assigned to closed
  • resolution set to fixed

New entries now get a new attribute set and old entries get a attribute old.

To make this working the jcreport needs to get access the old report. This is done by the new attribute oldReportFile in the jcreport ant task.

Note: See TracTickets for help on using tickets.