Details

    • Type: Question Question
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Component/s: None
    • Labels:
      None
    • Global Rank:
      17682

      Description

      I have a project I'm working on that needs to be pushed into Maven Central. The project currently resides in our own hosted Archiva. I'm currently going through the following guide:
      https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

      The problem I'm struggling with at the moment is how to structure the project requests. I have two major group IDs:
      com.force.sdk
      com.force.api

      These are both listed in our Archiva repo. The other dependency that's not in maven central is jmockit. Since I don't own that dependency, I was planning on using the 3rd party upload service:
      https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central

      com.force.sdk depends on com.force.api. com.force.sdk also depends on jmockit. Should I create two projects for each of the major group IDs and upload com.force.sdk first? Can I create a single project that encompasses both com.force.sdk and com.force.api? At what point should I upload the 3rd party artifact?

      Thank you very much for your help.

        Activity

        Naaman Newbold created issue -
        Juven Xu made changes -
        Field Original Value New Value
        Comment [ you only need to create one OSSRH project with groupId com.force, then you will be able to deploy any artifacts of groupId com.force.*

        you should upload 3rd party dependencies before you release your own project, to make sure release artifacts synced to central having all its dependencies in central as well.

        thanks,
        juven ]

          People

          • Assignee:
            Juven Xu
            Reporter:
            Naaman Newbold
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Date of First Response: