Hi Aaron,
Holy smokes! Excellent progress! My initial feedback (in addition to
"Holy Smokes! Excellent progress!"):
<entryattribute name="runtime" />
<entryattribute name="fileName" />
<entryattribute name="severity" />
<entryattribute name="message" />
<entryattribute name="type" />
<entryattribute name="line" />
<entryattribute name="column" />
<entryattribute name="data" />
Currently, the idea for sensor data types is to use <entryattribute> to
express the required fields that must be present in all instances of the
data in all contexts, and the PropertyMap to express the optional fields
that do not have to be present all of the time for the data to be valid.
Given that, I wonder which of the above are required and which are optional
for CodeIssue?
An initial guess:
Required Optional
runtime severity
fileName message
type line
column
data
what do you think?
Philip: please advise on whether I can do the following:
- import hackyCodeIssue into CVS
- commit new hackyAnt sensors (Emma, FindBugs, PMD, Checkstyle).
- commit new hackyAnt Jira2 sensor or blow away old Jira sensor.
- commit my changes to the hackyBuild build.xml and build.utils.xml
You could, but how desperate are you to get this into the 6.x release
stream? I ask this because I am currently planning for us to start the 7.x
repackaging process later this week, and so it will be more efficient to
simply integrate these as part of the 7.x release stream
(hackySdt_CodeIssue, hackySensor_Emma, hackySensor_FindBugs,
hackySensor_PMD, etc.) There's not going to be much additional development
in 6.x, so you could simply maintain your 'fork' of 6.x separately for now
until we formally move to 7.x. How does that sound?
Cheers,
Philip
