Creating integrations/opennms-vtdxml-collector-handler

Because VTD-XML is a GPL library, the XML Collection Handler
implementation was moved from protocols/xml to its own package in order
to create a separate RPM/DEB package for this optional handler.
Adding a debug message to estimate the duration of the timestamp parsing.
Got rid of Spring Security feature since it is provided in Karaf 2.3.4+.
Got rid of unnecessary function in ToStringBuilder.
Spelling fix.
Added Spring-instantiated classes to the OSGi Import-Package list.
Wrapped Spring context instantiation so that it uses the current class's
classloader so that the loading works properly in OSGi.
Refactored attribute type to mesh more to the sampler's Metric type.
Trying to fix the RPM generation (still fails)

./makerpm.sh
...
    Processing files:
opennms-plugin-collector-vtdxml-handler-1.13.2-0.20140502.1.noarch
    error: File not found by glob:
/home/agalue/opennms/target/rpm/BUILDROOT/opennms-1.13.2-0.20140502.1.x86_64/opt/opennms/lib/opennms-vtdxml-collector-handler-*.jar
add assembly for the vtdxml bits
Added some sanity-checking when adding RRD metadata.
missing debian bits for vtdxml
Fix up reduction-keys and add clear-keys for VMware.vminfo.events.xml
Fix for Bug NMS-6545

ResourceDao.findTopLevelResources() is returning duplicated data because
of storeByForeignSource.

Tested on the following scenarios:

1) All nodes are provisioned and storeByForeignSource is disabled (i.e.
all the RRD directories are like this: rrd/snmp/{nodeId}.
2) All nodes are provisioned and storeByForeignSource is enabled (i.e.
all the RRD directories are like this: rrd/snmp/fs/{fs}/{fid}
3) Hybrid environment, there are requisitioned nodes and discovered
nodes on the same installation with storeByForeignSource enabled. In
this case, the discovered nodes will have rrd/snmp/{nodeId} for the
RRDs, while the provisioned nodes will have rrd/snmp/fs

IMPORTANT: If storeByForeignSource is enabled and the RRDs are stored
under a directory like rrd/snmp/{nodeId}, those RRDs are going to be
ignored (because they must be stored under rrd/snmp/fs/{fs}/{fid})
Merge remote-tracking branch 'origin/1.12'

Conflicts:
	opennms-dao/src/main/java/org/opennms/netmgt/dao/ResourceDao.java
	opennms-dao/src/main/java/org/opennms/netmgt/dao/support/DefaultResourceDao.java
	opennms-model/src/main/java/org/opennms/netmgt/model/OnmsResource.java
	opennms-services/src/test/java/org/opennms/netmgt/statsd/ReportDefinitionTest.java
	opennms-webapp/src/main/java/org/opennms/web/svclayer/support/DefaultResourceService.java
	opennms-webapp/src/main/webapp/WEB-INF/jsp/KSC/index.jsp
Fixing compiling issues after merging the ResourceDao changes from 1.12
Be more verbose on Statsd's logging

Now you can see the data that potentially is going to be persisted, and
the data that it is actually going to be persisted.

Also, it is going to show a warning when there is no data. If all the
data to be considered for the report is NaN, the report is going to be
empty (and should not be persisted).
Fix for Enhancement NMS-6504 - Sort notifications by severity
Merge remote-tracking branch 'origin/1.12'

Conflicts:
	opennms-dao/src/main/java/org/opennms/netmgt/dao/support/RrdStatisticAttributeVisitor.java
	opennms-services/src/main/java/org/opennms/netmgt/statsd/DatabaseReportPersister.java
Minor cleanup.
Got rid of unused parameter on IndexStorageStrategy. Refactored it into the
collection/api project.