Hey Guys,
While working on converting my new Jira sensor to Version 7, I ran into a
couple of problems.
First off.. I'm making a new module called hackySensor_Jira2 instead of
directly replacing the hackySensor_Jira. I'm not sure why I'm doing
this, but I figured we could try it out first before officially changing
over. By the way, this new Jira sensor uses Apache's HttpClient to be
able to collect jira issues from login protected projects. It also
combines the specialized Ikayzo sensor functionality as optional
features. But, the functionality that has been supported by past
Jira sensors should also be supported in this new version. I believe Tim
was worried about that.
Here are the issues with Hacky Installer:
- hackyCore_Installer\lib\test\hackyinstaller.xml and
sensor.properties. I had to add the appropriate entries of Jira2 to
these files because it seems that you need to define the
ENABLE_JIRA2_SENSOR and define the sensor for the unit test to
pass. This is a little bogus, because any new sensors would have to
edit these files. (i didn't commit this.. i'll wait till i'm done
converting hackySensor_Jira2).
- It looks like hackyInstaller doesn't support installer.<sensor
name>.xml files that contain digits. See line 253 of
SensorXmlParser.
if
(fileName.matches(
"installer\\.[a-z]+\\.xml"
)
thus, I had to change my "installer.jira2.xml" to
"installer.jiratwo.xml". That is a little strange,
because in another part of the code, I see this:
if
(entryName.matches(
"sensors/installer\\.[a-z]+[0-9]?\\.xml"
)
So, I think the first if statement is a bug...
- it seems that we would eventually need a docbook chapter on how to
write these installers. For example, my local.build.xml file was a little
old and i was getting a NullPointerException in the installer code when
running the unit test. It took me a while to figure out that the
systemproperties in the makeJunit task wasn't defined correctly.
thanks, aaron
