Closed EvgeniGordeev closed 1 year ago
For our corporate usage we import the project to internal gitlab and deploy it to our internal repository by tweaking build.gradle
:
plugins {
id 'java'
id 'org.hibernate.build.maven-repo-auth' version '3.0.3' // use mvn settings.xml for nexus auth
id 'maven-publish'
}
group 'at.klausbetz'
test {
useJUnitPlatform()
}
java {
withSourcesJar()
}
publishing {
publications {
myJava(MavenPublication) {
from components.java
}
}
repositories {
maven {
name 'nexus-releases'
url "https://example.com/repository/maven-releases/"
}
}
}
This could be a great improvement!
Would you like to create a pull-request? I'd be more than happy to see you contribute to this extension 😄
@klausbetz PR is ready. The dependency in Maven will look like
<dependency>
<groupId>com.github.klausbetz</groupId>
<artifactId>apple-identity-provider-keycloak</artifactId>
<version>1.5.0</version>
</dependency>
For custom group id see https://jitpack.io/docs/#custom-domain-name.
I added a job for tags only - as soon as you create a release this job is proactively initiating a jitpack build.
Closed with #36
It seems to be pretty straightforward to push the artifact to the github based maven repository - https://jitpack.io/#klausbetz/apple-identity-provider-keycloak/1.4.0.
First build failed https://jitpack.io/com/github/klausbetz/apple-identity-provider-keycloak/1.4.0/build.log: