Publish library

[DavyHubrecht]

Any plans to publish this library to a maven repo?

[Pakisan]

@DavyHubrecht hi.

Yeah, I have plans to publish it in mid of September. Right now I'm testing it in a few side projects. If you need it in central maven repo, I will publish it after closing your issue #2 as 1.0.0-RC1. Are you ok with it?

[ITman1]

@Pakisan
Hello Pavel, I would like to thank you for creating AsyncAPI Java models and creating plugins on top of it. I did try to use your asyncapi-core for building AsyncAPI model in Java and tried it to push it into AsyncAPI UI React component. I did not hit any problem, but I had to clone this repository and use source code directly and that is why I would really love to see this library in Maven Central repository. May I ask you how does it go? What is the progress? Thank you.

[Pakisan]

@ITman1 hi. Thanks for feedback.

As you can read I planned to publish it in a mid of September, but after fixing of a bug DavyHubrecht didn't force me up to publish it. So I decided to make a few improvements before publishing RC-1.0 later.

You can find left tasks in project, binded to repo. Two tasks left. After closing them I will push it to maven central repo. I planned to do it on this weekends (14-15)

[Pakisan]

@ITman1 hi.

I Waiting response from asyncapi team about publishing. It's a problem with site ownership validation - com.asyncapi. It's required step before publishing

[ITman1]

@Pakisan
Thanks for a info. Maybe it would not be bad Idea to move your Java API models under AsyncApi project in general. Because your models seemed to me in very good shape. Maybe @stavshamir from SpringWolf project could leverage from it also. SpringWolf also has some minimal set of Java models, but not so extensive like this project. When I generated documentation using this project I missed only this one feature OneOf, but otherwise all went well for me.

[Pakisan]

@ITman1
As workaround I can publish to github packages for now.

Yeah, I know about lost properties in schema. I want to fix it on this week

[stavshamir]

@ITman1 I could definitely leverage @Pakisan library for springwolf, an infact we already discussed it, so thanks for the suggestion.

I also think that this library should be moved to the async api organization.

[Pakisan]

@ITman1 @stavshamir hi. Working on transfer to asyncapi repo

[derberg]

Welcome to AsyncAPI https://github.com/asyncapi/java-asyncapi/ 🥳

[Stmated]

So what's the status of getting this up in Maven? Or is this up on Github repo? (Which I know nothing about how to work with)

[Pakisan]

@Stmated hi.

I think that asyncapi-core will be published before end of the next week (13 december).

[Pakisan]

Looks like asyncapi-core will be published before end of the year. No way to do it early. I working hard on IDEA plugin

[Pakisan]

waiting for repository approving - https://issues.sonatype.org/browse/OSSRH-63280

[Pakisan]

Next artifacts has been deployed to https://oss.sonatype.org/content/repositories/snapshots/

• asyncapi-core
• asyncapi-plugin-maven

SNAPSHOT versions are not synchronized to the Central Repository. If you wish your users to consume your SNAPSHOT versions, they would need to add the snapshot repository to their Nexus Repository Manager, settings.xml, or pom.xml. Successfully deployed SNAPSHOT versions will be found in https://oss.sonatype.org/content/repositories/snapshots/

To download them you need to enable snapshot repository. After that you can obtain them via:

<dependency>
  <groupId>com.asyncapi</groupId>
  <artifactId>asyncapi-core</artifactId>
  <version>1.0.0-SNAPSHOT</version>
</dependency>

<dependency>
  <groupId>com.asyncapi</groupId>
  <artifactId>asyncapi-maven-plugin</artifactId>
  <version>1.0.0-SNAPSHOT</version>
</dependency>

UPD:
Thinking how to do it better. Looks like will be better to deploy in release repo as EAP in few days

[ITman1]

Publishing into release repo of Maven Central is definitelly better way to go no matter what classifier or version suffix you put behind it 😉. Will wait for it as using SNAPSHOT is kind of dirty solution as it can easily change under your hands. Anyway thank you for your effort Pakistan 👍.

[Pakisan]

I have deployed eap version to central maven repo. But until sync it will not be available in search results from https://search.maven.org. I guess that for now it's possible to obtain it via

<dependency>
  <groupId>com.asyncapi</groupId>
  <artifactId>asyncapi-core</artifactId>
  <version>1.0.0-EAP</version>
</dependency>

[Pakisan]

Good news, everyone!

EAP version is officially available at central maven repository

[Pakisan]

@derberg I think we can close this issue