-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
None
-
None
-
False
-
-
False
-
-
[INFO] Moving artifacts with tag 'mvc-krazo-feature-pack-2.0.1.Final' from 'wildfly-extras-staging' to 'releases' [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for WildFly Jakarta MVC with Krazo -- Parent 2.0.1.Final: [INFO] [INFO] WildFly Jakarta MVC with Krazo -- Parent ........... FAILURE [15:00 min] [INFO] WildFly Jakarta MVC with Krazo -- Local Galleon Content SKIPPED [INFO] WildFly Jakarta MVC with Krazo -- Subsystem ........ SKIPPED [INFO] WildFly Jakarta MVC with Krazo -- Shared Galleon Content SKIPPED [INFO] WildFly Jakarta MVC with Krazo -- Feature Pack ..... SKIPPED [INFO] WildFly Jakarta MVC with Krazo -- TCK Runner ....... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 15:17 min [INFO] Finished at: 2025-11-05T21:36:17-06:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.sonatype.plugins:nxrm3-maven-plugin:1.0.13:staging-move (default-cli) on project mvc-krazo-parent: Move components was unsuccessful (500 response from server). Reason: status code: 500, reason phrase: Internal Server Error -> [Help 1]
I report this as 'Minor' because behind the scenes it looks like the move happened:
I checked that page right after the failure and at the time the mvc-krazo-tck-runner component was still reported as being in wildfly-extras-staging.
Note that a long time elapsed before the failure. Also, in general in recent days nxrm3-maven-plugin deployment operations are very slow, back to the way there were several weeks ago.
