Migration from 2.14.16-01 to 3.22.1-02

Nexus Repository Manager
#1

Sorry for the newbie question.

But we have migrated our existing repos from our old nexus 2.14.16-01 server to the new 3.22.1-02

The repository structure seems the same. When browsing the repository from the nexus ui.

The old curl call was.

curl -v -F “r=releases” -F “g=com.Balloons.xyz.bubbles” -F “a=bubbles.api” -F “v=1.0.$BUBBLESAPIBUILDNUMBER” -F “p=tar.gz” -F “file=@./xyz-bubbles-api.tar.gz” -u squeakadmin:notrealpassword http://abc-centos.us-Balloons.root.Balloons.com/nexus/service/local/artifact/maven/content

The new one is

unset https_proxy
unset HTTPS_PROXY

curl -X POST -F “r=releases” -F “g=com.Balloons.xyz.bubbles” -F “a=bubbles.api” -F “v=1.0.$BUBBLESAPIBUILDNUMBER” -F “p=tar.gz” -F “file=@./xyz-bubbles-api.tar.gz” -u squeakadmin:notrealpassword https://xyz-nexus.saas-n.com/repository

But I’m getting a

Error 400
Bad Request

HTTP method POST is not supported by this URL
</divError 400 Bad Request
HTTP method POST is not supported by this URL
</div

Is the use of the parameters or path different for 3.22.1-02? I’m thinking this maybe a path issue. But I’m not sure. The new nexus is https now.

Any pointers would be appreciated

#2

In the admin section of the UI there is a section called Swagger, there is an upload component API entry there if you aren’t using Maven to deploy.