Dependency issues on Master and Develop branch preventing local deployment

[lukabartolicFS]

After successful configuration and setup of DataCustodian solution (GreenButtonAlliance/OpenESPI-DataCustodian-java#275 (comment)), in order to have complete development sandbox environment setup and to test all DC and TP scenarios using SOAPUI project, ThirdParty implementation also had to be configured (next to DataCustodian and GreenButtonCMDTest projects).

During TP setup several errors occured:

1. On MASTER branch, Tomcat server failed to start:

[ERROR] Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.0:run (default-cli) on project open-espi-third-party: Could not start Tomcat: Failed to start component [StandardServer[-1]]: Failed to start component [StandardService[Tomcat]]: Failed to start component [StandardEngine[Tomcat]]: A child container failed during start

• during debugging it was found that Tomcat, Java, Java Servlet and Tomcat Maven Plugin versions were outdated and incompatible

2. On DEVELOP branch, some of the potential issues from 1) seemed to be resolved, but Tomcat server again failed to start with the same error response like in 1).

• after inspecting the pom.xml file and dependencies, it was found that Tomcat Maven Plugin version was correctly updated, but Tomcat, Java and Java Servlet versions were mismatched.

Solution for running TP: ThirdParty solution was successfully built and ran using DEVELOP branch after changing following settings:

• java.version from 1.7 to 1.8
• javax-servlet.version from 3.0.1 to 3.1.0
• tomcat-jdbc.version from 7.0.42 to 7.0.47

This resolved setup issues faced in 1) and 2) and the TP was correctly served on localhost:8080/ThirdParty.