Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Publishing the core library to Maven central #104

Closed
metc opened this issue May 7, 2015 · 3 comments
Closed

Publishing the core library to Maven central #104

metc opened this issue May 7, 2015 · 3 comments
Assignees
@metc
Labels
enhancement
Milestone
Version 1.2 - Sep...

Comments

@metc
Copy link
Contributor

metc commented May 7, 2015

I propose to publish the core library Jar to the Maven central repository (to Sonatype Nexus OSS for instance). This will:

  1. help to maintain snapshots and release versions,
  2. automating and simplifying our release process,
  3. resolve our build dependencies nightmares between projects,
  4. and finally this will encourage (wide) adoption.

This is a long-term proposal. We can still use Ant as build system, or we can switch to Maven or Gradle but this is not mandatory.
@metc metc added the question label May 7, 2015
@pmudry
Copy link
Contributor

pmudry commented May 28, 2015

This sounds wonderful. I don't understand the implications though and how the project would be used... Can you elaborate a bit?

@metc
Copy link
Contributor Author

metc commented Aug 6, 2015

We can now publish any artifacts with the group Id ch.hevs.* into the Maven Sonatype repository.

The request was made for another project and we finally get the authorization to publish any ch.hevs.* package. That's great, thanks @cm0x4D 🎶

Detailed info available here: https://issues.sonatype.org/browse/OSSRH-16923

@metc metc added enhancement and removed question labels Dec 8, 2015
@metc metc self-assigned this Dec 8, 2015
@metc metc mentioned this issue Dec 8, 2015
Closed
metc added a commit that referenced this issue Dec 12, 2015
@metc
Added Maven projects.
280548d 
A parent Maven project is used to share common definitions. It also defines all available modules.
The gdx2d-lib is a Maven module which contains the gdx2d library only (without any demo).

The library contains all needed libgdx dependencies. Pom files include all requirements needed to push the artifact to Maven Central (or jCenter). Requirements are defined here: http://central.sonatype.org/pages/requirements.html

Related to #103 and #104
@metc metc added this to the Separate demos and library and push to Maven Central milestone Dec 12, 2015
@metc metc mentioned this issue Apr 1, 2016
Merged
@metc
Copy link
Contributor Author

metc commented Apr 1, 2016

Both gdx2d-core and gdx2d-desktop artifacts are now available on Maven Central.

See https://repo1.maven.org/maven2/ch/hevs/gdx2d/
The javadoc is available online here: http://www.javadoc.io/doc/ch.hevs.gdx2d/gdx2d-desktop/1.2.0

@metc metc closed this as completed in #116 Apr 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@metc metc

Labels
enhancement
Projects
None yet
Milestone
Version 1.2 - Separate demos and libr...
Development

No branches or pull requests
2 participants
@metc @pmudry