Java Server SDK Dependency
We have now switched over to using the Vonage branding so this project needs to use the com.vonage group id instead of the com.nexmo group id in the pom.xml files located in the /nexmo-spring-boot-starter and /nexmo-spring-boot-autoconfig.
The property name also needs to be changed from nexmo.version to vonage.version which can be found at the bottom of the pom.xml file located at the root of the project.
Updating Imports
Once the dependency is changed, the imports in the code that throw an error will have to be updated to com.vonage.
Spring Boot Dependency
The Spring Boot also needs to be updated to the latest. The Spring Boot version property can be found in the pom.xml file at the root of the project.
Once the version is updated from the root, the other pom.xml files need to be checked to make sure any other spring dependencies are using the latest version
Update nexmo-starter Version
Update nexmo-starter version to 2.2.0 in all the pom.xml files that include that dependency.
Testing
Once all imports have been made run the mvn clean install command make sure the project builds successfully and run the project locally to make sure it still works.
Update README
Update the readme to reflect the vonage dependency and the correct version under the Customize Nexmo Client Version section
Create a new table under the current table at the bottom of the README with the following column headers Nexmo Spring Boot Starter and Vonage Java Client. The first entry should use v2.0.0 as the Nexmo Spring Boot Starter version and v5.5.0 as the Vonage Java Client version.
Java Server SDK Dependency
We have now switched over to using the Vonage branding so this project needs to use the
com.vonagegroup id instead of thecom.nexmogroup id in thepom.xmlfiles located in the /nexmo-spring-boot-starter and /nexmo-spring-boot-autoconfig.The property name also needs to be changed from
nexmo.versiontovonage.versionwhich can be found at the bottom of the pom.xml file located at the root of the project.Updating Imports
Once the dependency is changed, the imports in the code that throw an error will have to be updated to
com.vonage.Spring Boot Dependency
The Spring Boot also needs to be updated to the latest. The Spring Boot version property can be found in the
pom.xmlfile at the root of the project.Once the version is updated from the root, the other pom.xml files need to be checked to make sure any other spring dependencies are using the latest version
Update
nexmo-starterVersionUpdate nexmo-starter version to 2.2.0 in all the pom.xml files that include that dependency.
Testing
Once all imports have been made run the
mvn clean installcommand make sure the project builds successfully and run the project locally to make sure it still works.Update README
Update the readme to reflect the vonage dependency and the correct version under the Customize Nexmo Client Version section
Create a new table under the current table at the bottom of the README with the following column headers Nexmo Spring Boot Starter and Vonage Java Client. The first entry should use
v2.0.0as the Nexmo Spring Boot Starter version andv5.5.0as the Vonage Java Client version.