Uploaded image for project: 'repository.jboss.org/nexus'
  1. repository.jboss.org/nexus
  2. NEXUS-1075

Sometimes maven client nxrm3:staging-move has to forcibly closed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • Q1CY26
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      This happened to me yesterday, moving WildFly Core project (68 modules) from wildfly-staging to releases repo.

      The staging-move goal took a lot of time. I left the laptop running during the night. The artifacts were all successfully moved, but the client maven gola execution never ended, and I had to close it forcibly with CTRL-C

      At that point, the client did not get any feedback on whether the movement completed successfully or not, so you are forced to check the tag and verify that all the artifacts were moved before closing the client.

              dhladky@redhat.com David Hladky
              yborgess1@redhat.com Yeray Borges Santana
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: