-
Notifications
You must be signed in to change notification settings - Fork 22
Add artifact to Maven Central #2
Comments
What is roadmap to get this artifact available in maven central? |
@harishyarlagaddas there's no official push right now. My team has a ticket for it on the backlog, but it's not a priority right now. I might take a crack at it in my free time in the next couple weeks. |
@mac9416 , any update on this? |
@paravatha this is still on my radar, but hasn't been a high enough priority yet. My focus for the moment is a Scala client. Once I have something set up to push those artifacts, it can probably be adapted for Java. |
@mac9416 any update on this? |
@paravatha I changed jobs to one that didn’t need the client, and I haven’t had a chance to pursue it personally. I’ll post back if I pick it back up. |
Maybe, in the meantime, it would be a good consideration to just publish the Packages also to jitpack? |
I've created an MR, so the project can be built using jitpack.io Until it's merged, you can use it with the settings here: https://jitpack.io/#vilmosnagy/argo-client-java/build_with_jitpack-SNAPSHOT |
It would be great if there were an artifact on Maven Central so folks don't have to build the client for themselves.
Ideally this would be an automated process pushing to an "official" argoproj groupid.
For now I think a one-off push to a non-official groupid and a markdown doc explaining the process would suffice. I'll probably try to take a crack at both of those soon.
The text was updated successfully, but these errors were encountered: