Jenkins Pipeline Nexus Stage

My Jenkins pipeline for a Spring Boot 2.6.x service currently jumps straight to the Deploy stage. I need one extra, fully-scripted stage that will:

• Archive the built JAR/ZIP,
• Push that artifact to our Nexus repository, and
• Trigger the deploy job by pulling the artifact back from Nexus into the Development environment.

You’ll work directly in the existing Jenkinsfile (declarative pipeline) and wire any necessary credentials or repository definitions so the flow is completely automated. A quick readme or inline comments that explain variables, Nexus URLs, and how to extend the same logic to Staging or Production later will be appreciated.

Acceptance criteria
– Successful pipeline run shows the new stage after Build/Test, before Deploy.
– Artifact appears in the correct Nexus path with proper version/tag.
– Deploy stage fetches exclusively from Nexus, not from the workspace.
– Job remains compatible with Spring Boot 2.6.x projects.

If you’ve configured Jenkins + Nexus integrations before, this should be straightforward; please share a short note on similar setups you’ve done so I can jump right into testing your solution.