Rational Software Analyzer Target - Resource directory
Hi,
I am using Rational Software Analyzer 7.1 together with a Rational Team Concert Build 2.0.0.2 system. I linked both together as described here: http://publib.boulder.ibm.com/infocenter/rsarhelp/v7r1/topic/com.ibm.xtools.analysis.rsar.common.doc/topics/t_rtc_build.html Could it be that it is NOT possible to use properties such as ${buildLabel} right within the "Rational Software Analyzer Target - Resource directory" text field? Each time I use properties RSAR does not find any projects to be analyzed which gives me the impression, that such properties won't be expanded. If I use an absolute path that does not contain any properties, RSAR at least starts analyzing projects. Cheers Daniel |
Accepted answer
So it looks like the RSAR build definition configuration element is missing a special property needed to indicate that it supports property substitution. They suggested raising an APAR, but I'm trying to find a good contact on the RSAR team for you to talk directly to.
Daniel Stefan Haischt selected this answer as the correct answer
|
4 other answers
It should be possible to use build property substitutions, assuming the RSAR configuration supports substitutions (it may not).
One thing to watch out for is if the substitution introduces a space, in which case you may need to add quotes around the path. The build log should give a trace of which substitutions were performed, so you can see whether the RSAR target directory field gets the substituted value, and whether it has spaces. |
Hi Nick,
It should be possible to use build property substitutions, assuming the RSAR configuration supports substitutions (it may not). Good point to have a look at the build log. That's the variabl substitution section of the build log: 2010-11-26 23:35:33 [Jazz build engine] running on host: modean As far as I can tell, it's not substituting RSAR specific settings. What do you think? Thanks! Cheers Daniel |
That's correct, it doesn't look like it's applying property substitutions for the RSAR configuration properties. I've asked the RSAR team whether it's a known problem, and either they or I will follow up here.
|
That's correct, it doesn't look like it's applying property substitutions for the RSAR configuration properties. I've asked the RSAR team whether it's a known problem, and either they or I will follow up here. Great! Thanks Nick, appreciated! I have a few other observations I made while using RSAR together with RTC. Maybe I could share them with the RSAR team too. If appropriate we could as well use an IBM internal communication channel to communicate with the RSAR team. Thanks! Daniel |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.