Skip to content
This repository has been archived by the owner on Nov 14, 2023. It is now read-only.

Decide on groupId #4

Closed
io7m opened this issue Feb 21, 2017 · 7 comments
Closed

Decide on groupId #4

io7m opened this issue Feb 21, 2017 · 7 comments

Comments

@io7m
Copy link
Collaborator

io7m commented Feb 21, 2017

Right now, the bundles are using a provisional com.io7m.bundles groupId. This obviously needs to be changed to something else prior to pushing to Central.

@darxriggs
Copy link

Thanks for your effort in providing OSGI bundles.

Do you know when the 1st release will be available? I am really looking forward to.

@io7m
Copy link
Collaborator Author

io7m commented May 10, 2017

Hello!

I'll be pushing these to Central on the day after the next LWJGL release. We need to decide on a groupId to use, but there are no other barriers to release.

@darxriggs
Copy link

Wow that was fast. Sounds great. I'll ask the LWJGL guys about the next release date.

@Spasi
Copy link
Member

Spasi commented May 10, 2017

The current 3.1.2 snapshot is a release candidate. I'm giving it a few more days for users to report any issues.

@io7m
Copy link
Collaborator Author

io7m commented May 10, 2017

@Spasi: Might I suggest org.lwjgl.osgi?

I obviously don't need or want permissions on Sonatype to push to the entirety of org.lwjgl.* so org.lwjgl.osgi would be a straightforward way to put these OSGi bundles into their own partition. The osgi suffix would be extremely unlikely to conflict with any future additions to LWJGL.

The Maven dependencies would look like:

<dependency>
  <groupId>org.lwjgl.osgi</groupId>
  <artifactId>org.lwjgl.opengl</artifactId>
  <version>3.1.2</version>
</dependency>

... Which would be fairly unsurprising for anyone familiar with OSGi and Maven.

@Spasi
Copy link
Member

Spasi commented May 10, 2017

I agree, lets go with org.lwjgl.osgi. It's the cleanest solution.

We'll also add an OSGi toggle in the build configurator to make the generated scripts use the new groupId.

io7m added a commit that referenced this issue May 10, 2017
@io7m
Copy link
Collaborator Author

io7m commented May 16, 2017

I've just pushed 3.1.2 to Central, but it may take a few hours for Sonatype to enable syncing and for the syncing to actually take place.

@io7m io7m closed this as completed May 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants