Release v4 version under a different artefact name #76
Description
What problem does your feature request address?
Iterative migration from v3 to v4 of the API needs both libraries to be present on the classpath. However, the artifacts are named equally which creates some challenges for Gradle based projects (the latest version is taken).
To solve the problem, some non-common approaches need to be taken, for example shadow jar, multiple configurations, repackaging, etc.
It would help if the major version was separated by the artefact name as well (not just the package).
Describe the desired solution
Differentiate the artefact by name as well, for example: com.chargebee:chargebee-java-v4
Alternatives considered
Shadow jar Gradle plugin, multiple configurations approach, repackaging the v3 jar under another name.
Additional context
No response