Thanks. I'll take it over and deploy it to hackydev.
Cool. Let me know if you have any questions about the implementation
of jira2. I assume you are going to write the docbook for this as well?
pMap thing can be found at
http://hackydev.ics.hawaii.edu/hackyDevSite/doc/evolutionarySDT.html
Thanks. I actually looked through that and it helped a little. This
doc seems to explain eSDTs more that it does pMap. I finally found
the portion of the doc that showed the use of SensorDataPropertyMap
construct a pMap was hidden all the way down in section 3.1.4 (in the
TestEvolSdt.java example). After reading this doc, I'm still a little
confused on why the pMap has to be encoded and decode. My guess is
that we couldn't come up with a good delimiter for the key-value
pairs. I was hoping for a HTML doc about writing a sensor that uses
pMap. I'm sure that it will be coming in the Developer docbook chapters.
Anyway, I think I figured it out. In fact, it wasn't that hard.
thanks, aaron
At 10:47 PM 1/25/2006, (Cedric) Qin ZHANG wrote:
Thanks. I'll take it over and deploy it to hackydev.
pMap thing can be found at
http://hackydev.ics.hawaii.edu/hackyDevSite/doc/evolutionarySDT.html
Cheers,
Cedric
Aaron Kagawa wrote:
Could you please advise the status of code in hackySensor_Jira2?
Jira2 has been working for a while, at least in my environment. And
Julie helped me complete the installer for it. But, it it doesn't
use the pMap and it doesn't have a doc book.
thanks, aaron
At 05:02 PM 1/25/2006, you wrote:
Hi, Julie and Aaron,
Could you please advise the status of code in hackySensor_Jira2?
I need the sensor to send additional piece of information: fix
version. Fortunately, this information is already in the xml file
generate by issue extractor. So, actually sending this information
would be simple. After discussion with Philip, we decide put it in
pMap with attribute name "FixVersion".
If hackySensor_Jira2 code ready for deployment, I guess I'll take
it over, adding "fix version" and put it on hackydev. I hope I
could get everything done by this weekend so that telemetry
streams can be generated on the wall. (Apart from the sensor, I
still have DailyProjectIssue, IssueReducer to modify).
Anyway, please advise status.
Thank you.
Cedric
Content-Type: message/rfc822;
name="Issue sdt \"fix version\" not captured by the sensor"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename*0="Issue sdt \"fix version\" not captured by the sensor"
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 25 Jan 2006 16:47:16 -1000
From: "(Cedric) Qin ZHANG" <[EMAIL PROTECTED]>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: [email protected]
Subject: Issue sdt "fix version" not captured by the sensor
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Issue sdt does not have a field called "fix version". How hard
would it be for jira sensor 2 to get this information?
Thanks.
Cedric
