Re: Creating custom propertis plugin

I have never actually used the registerCustomProperty(), so I don't 
think I can add much. I wonder if it could be used via a direct call (at 
least for testing), and later any missing "addxxx()" methods could be added?

Sorry, but I don't know the details of the intended use case here. This 
feels like a case where I wish we had a unit test that could show us the 
intent.

Dan (R)



Date: Wed, 03 Aug 2011 22:42:38 +0200
From: "Ing. Daniel TIHELKA Ph.D." <[email protected]>
Subject: Re: [Cruisecontrol-devel] Creating custom propertis plugin
To: [email protected]

Hallo,
I have looked around little bit and I have found the following:

The only place where raw

   PropertiesPlugin#loadProperties(Map<String, String>, boolean)

is called, is:

   PropertiesPlugin ProjectXMLHelper#registerCustomProperty(Map<String, 
String>,
             Element, ResolverHolder, boolean, PluginRegistry)

which is called from:

   CruiseControlConfig.handleCustomRootProperty(Element)

which is then called from:

   CruiseControlConfig.parse(Element)


However, when I debugged it with my plugin configuration (see my 
previous mail), such methods are never called (I have put a breakpoint 
there and debugged the instantiation of  new XMLConfigManager(projectFile)).


So, the question is - what to do now? In fact. I don't know how to 
create custom properties plugin. Simple implementation of 
PropertiesPlugin interface seems not to be enough.

Do you have an idea what needs to be changed/adjusted to get it work 
correctly?

Thank you very much for your help.
Best regards,
Dan T.


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1