Proxy name should be customizable and not tied directly to project.name

[ericdahl]

We occasionally like to deploy copies of proxies under different names for testing in a dev environment.

Unfortunately, this plugin seems to only allow the proxy name to be the same as the maven project name. There's no way to override the proxy name. Wouldn't it be more consistent to have the proxy name be defined in a property like apigee.env or apigee.org ? Or at least have it be overrideable via a flag?

[msadasivam]

The name of the API bundle can be changed using the "name" element in pom.xml.

<modelVersion>4.0.0</modelVersion>
<groupId>apigee</groupId>
<artifactId>forecastweatherapi</artifactId>
<version>1.0</version>
<name>forecastweatherapi</name>                                <=====
<packaging>pom</packaging>

A duplicate deployment usually fails as a basepath conflict happens. So some form of pre-deployment customization is expected.

[gbansal3]

you can also use the parameters in mvn command and use them to update the name of the artifact from environment to environment, we are using that in our project repository.