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

Move to Sonatype #1

Open
stonier opened this issue Nov 1, 2013 · 0 comments
Open

Move to Sonatype #1

stonier opened this issue Nov 1, 2013 · 0 comments
Milestone

Comments

@stonier
Copy link
Contributor

stonier commented Nov 1, 2013

A final move to sonatype would be the ideal place for a ros maven repository. Benefits:

  • Long term it forces us to sync with mavencentral.(the ultimate repository of all things java)
  • We can scale (this git repo will quickly becoming too big)
  • People can manage their own uploads and contributions
    • No human intensive bottleneck at the pull request stage here.

For now though this would be a big job. Areas that need to be worked on:

  • Upgrade the gradle logic for signed, automated publication to sonatype.
  • Our rosjava 3rd party dependencies need to become mavencentral dependencies
    • we have quite a few custom artifacts in here
    • lots of testing!
    • Perhaps recreate some artifacts ourselves and push that to sonatype.
missxa added a commit to Roboy/rosjava_mvn_repo that referenced this issue Jun 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant