-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add apigw-maven-plugin to Maven Central Repository #48
Comments
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
|
Hi,
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 . |
I could not find it there: https://search.maven.org/search?q=apigw-maven-plugin
The text was updated successfully, but these errors were encountered: