All basic component classes now have a public constant
INSERTION_POINT, defined relative to its parent. Use this constant
rather than the literal where possible.
Use it for Node, Agent, AgentManager, PluginManager, Blackboard,
DomainManager, and Plugin (in this case defined in PluginBase, all
other cases defined in the so-named class/interface).

Fix bug 2482:
InitializerService.getComponentDescriptions should be given the
_parent_ insertion point, and it will return only items _below_ that
point. That is how the DBInitService works. File is different, since
it is just reading pre-split files. Arguably INIParser.parse or
FileInitializerServiceProvider should be modified so behavior matches,
but I have not done that here.
If users want items of a particular insertion point, specify the
parent, and then use
ComponentDescriptions.extractInsertionPointComponent(<insertion
point>)

Add a little debug/info level logging on loading of components.
All basic component classes now have a public constant
INSERTION_POINT, defined relative to its parent. Use this constant
rather than the literal where possible.
Use it for Node, Agent, AgentManager, PluginManager, Blackboard,
DomainManager, and Plugin (in this case defined in PluginBase, all
other cases defined in the so-named class/interface).
Add debug/info logging of use of this service. Add comments reminding
that getComponentDescriptions returns only components _below_ the
given point.
Fix bug 2482:
InitializerService.getComponentDescriptions should be given the
_parent_ insertion point, and it will return only items _below_ that
point. That is how the DBInitService works. File is different, since
it is just reading pre-split files. Arguably INIParser.parse or
FileInitializerServiceProvider should be modified so behavior matches,
but I have not done that here.
If users want items of a particular insertion point, specify the
parent, and then use
ComponentDescriptions.extractInsertionPointComponent(<insertion
point>)
Add some debug/info logging on where Node being initialized
from. Additionally, define 2 new constants for the System properties
specifying the filename to load from or the experiment.id
Use the 2 new constants in InitializerServiceProvider for the System properties
specifying the filename to load from or the experiment.id.
Remove useless code examining those properties - that is done _solely_
in InitializerServiceProvider.

All basic component classes now have a public constant
INSERTION_POINT, defined relative to its parent. Use this constant
rather than the literal where possible.
Use it for Node, Agent, AgentManager, PluginManager, Blackboard,
DomainManager, and Plugin (in this case defined in PluginBase, all
other cases defined in the so-named class/interface).
All basic component classes now have a public constant
INSERTION_POINT, defined relative to its parent. Use this constant
rather than the literal where possible.
Use it for Node, Agent, AgentManager, PluginManager, Blackboard,
DomainManager, and Plugin (in this case defined in PluginBase, all
other cases defined in the so-named class/interface).

Fix bug 2482:
InitializerService.getComponentDescriptions should be given the
_parent_ insertion point, and it will return only items _below_ that
point. That is how the DBInitService works. File is different, since
it is just reading pre-split files. Arguably INIParser.parse or
FileInitializerServiceProvider should be modified so behavior matches,
but I have not done that here.
If users want items of a particular insertion point, specify the
parent, and then use
ComponentDescriptions.extractInsertionPointComponent(<insertion
point>)

Add a little debug/info level logging on loading of components.
All basic component classes now have a public constant
INSERTION_POINT, defined relative to its parent. Use this constant
rather than the literal where possible.
Use it for Node, Agent, AgentManager, PluginManager, Blackboard,
DomainManager, and Plugin (in this case defined in PluginBase, all
other cases defined in the so-named class/interface).
Bug 1571: ComponentPlugin is now a trivial extension of
BlackboardClientComponent.

One significant change:
getBindingSite returns a generic BindingSite, not a
PluginBindingSite. It _may_ however be cast to a PluginBindingSite,
which is what it will be.

However, users should have no need to make that cast.
The primary reason subclasses make that cast is to get the
AgentIdentifier, which may be retrieved directly: juse call
getAgentIdentifier(), (which uses the AgentIdentificationService).
Drop no-longer-necessary cast to PluginBindingSite for access to AgentIdentifier
Fix another use of PluginBindingSite, using AgentIdentificationService instead
Fix another use of PluginBindingSite, using AgentIdentificationService instead
Fix another use of PluginBindingSite, using AgentIdentificationService instead
Make publishWhatever log or throw unchecked exception rather than return false (bug 168)
Fixing the report task predicate.
Initial pass at separation of planning from core
Clean up AllocationResult a bit.  Fixes bug 1968, supports bugfix for 2509
Fix javadoc - was way out of date
Removed BlackboardMetrics planning dependency
Added new "int getBlackboardCount(Class cl)" API
Use new non-planning blackboard metrics