#000 Removed/Upgraded libs that's pulling older versions of xerces

[zabil]

This to fix the problem of

WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Warning:  org.apache.xerces.parsers.SAXParser: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized.
Warning:  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized.

These warnings are printed when you have xerces on the classpath. A newer version of the JDK(8) does not fix this. The only solution is to get rid of xerces (which now comes bundled with the idk) as a transitive dependency.

This pull request fix it only on some modules.

Apache shindig (used on our app) hard wires the xerces dependency and modules referring shindig will still print this error. For a long term solution we should upgrade the version of Apache shindig.

[jyotisingh]

This changes make sense, but would not fix the warnings when Go server runs. Probably affects test runs only. Anyway, could you sync your changes with upstream so I could proceed with the merge.

[ketan]

This changes make sense, but would not fix the warnings when Go server runs. Probably affects test runs only. Anyway, could you sync your changes with upstream so I could proceed with the merge.

@jyotisingh I've seen these warnings in production code as well.

[zabil]

Will be solved in production code once we finish this #1169

[jyotisingh]

@ketan - Yes the warnings show up in production as well, thats exactly what I meant when I said when Go server runs. I am okay to merge these changes as the dependencies which were removed in the pr did not make sense in the first place.