Add apigw-maven-plugin to Maven Central Repository
remisbaima opened this issue · 3 comments
I could not find it there: https://search.maven.org/search?q=apigw-maven-plugin
The plugin package is not hosted on Maven Central but is hosted on GitHub Packages.
To use the plugin within you Maven project add the GitHub Packages repository to your pom.xml
<repositories>
...
<repository>
<id>github</id>
<name>Axway API Gateway Maven Plugin Packages</name>
<url>https://maven.pkg.github.com/Axway-API-Management-Plus/apigw-maven-plugin</url>
</repository>
</repositories>
Hi,
Would it be possible to put it in the Maven Central Repository?
Reasons:
- the GitHub Packages requires a token: https://help.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages
- the issue is that I want to integrate it in our CICD pipeline and we do not have an enterprise GitHub, so using my private GitHub account token is not feasible.
- besides our internal Maven mirror (which is used by the CICD Jenkins) is currently only allowed to mirror the Maven Central Repository.
BTW... in the project pom.xml the GitHub Packages reference has to also be put inside pluginRepositories:
...
<repositories>
<repository>
<id>github</id>
<name>Axway API Gateway Maven Plugin Packages</name>
<url>https://maven.pkg.github.com/Axway-API-Management-Plus/apigw-maven-plugin</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>github</id>
<name>Axway API Gateway Maven Plugin Packages</name>
<url>https://maven.pkg.github.com/Axway-API-Management-Plus/apigw-maven-plugin</url>
</pluginRepository>
</pluginRepositories>
<dependencies>
<dependency>
<groupId>com.axway.maven.plugins</groupId>
<artifactId>apigw-maven-plugin</artifactId>
<version>${axway.maven.plugin.ver}</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>com.axway.maven.plugins</groupId>
<artifactId>apigw-maven-plugin</artifactId>
<version>${axway.maven.plugin.ver}</version>
<extensions>true</extensions>
</plugin>
</plugins>
</build>
</project>
Moving the plugin to Maven Central is not that easy because of Maven Central has some policies which doesn't allow me to push it to Maven Central.
I labeled this issue as "enhancement". So it may be moved to Maven Central for future releases.
Btw. you are right, the repository has to be specified with the .