Skip to content

Conversation

Sanne
Copy link
Member

@Sanne Sanne commented Mar 3, 2019

<groupId>org.infinispan.quarkus</groupId>
<artifactId>infinispan-hibernate-cache-quarkus</artifactId>
<version>${project.version}</version>
<groupId>org.hibernate</groupId>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's probably too late but, IIRC, we decided to not push any new artifacts at the root of org.hibernate. We moved all our artifacts to specific subdirectories.

On Zulip, you initially suggested org.hibernate.quarkus.

BTW, wondering how it will be synchronized to Maven Central? I'm not sure the root of org.hibernate is automatically synchronized to Central or if we have to specify specific directories.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yea, your two questions are related.

I preferred org.hibernate.quarkus but I won't get a new groupId approved on time. So piggi-backing on org.hibernate for now, as anything in there published on JBoss Nexus gets synched to Maven Central - and doesn't need signatures either.

We'll move it to a better group when the fate of this project gets clearer - there's also the possibility that it gets absorbed in ORM6.

Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The artifact is now available on Central.

@gsmet gsmet merged commit d29eec0 into quarkusio:master Mar 4, 2019
@gsmet gsmet added this to the 0.11.0 milestone Mar 4, 2019
@Sanne Sanne deleted the InfinispanCacheSeparation branch March 4, 2019 10:36
maxandersen pushed a commit to maxandersen/quarkus that referenced this pull request Nov 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants