Jira: NSDWAN-1 : Removing vspk version number from packages.

[mkarnam]

Description:-

• Whenever we upgrade vspk in SDWAN portal, we have to replace all the instances of version numbers in our code base. If API version number is not present in package names, it is easy for us to switch between vspk versions. Version number is anyway maintained in pom.xml to differentiate between versions. Don't see much of a use for maintaining version number at package level. If there is no harm in removing version number from package names, please approve this pull Request.

Changes: -

• Updated APIVersionWriter to remove version number from packages.

Testing:

• Generated VSPK java and checked there is no version number in vspk java

[pdumais]

Can you confirm the resulting code by posting an example usage?

Also, this would need to be postponed to the next major release since this will create a backward incompatibility.

@pdellaert can comment some more.

[pdellaert]

@pdumais, @mkarnam , isn't this going to break any integration in the world? Everybody using the Java VSPK will have to change their imports?

So yes, this will have to be delayed until the next major release.

[pdumais]

Yes it will. Waiting for the next major release is preferable since we will have to change the import anyway then (since the version number is part of the imported name)

[pdellaert]

Sure, will track this for then :)