If your need is to deploy some artifact (maybe a json text file) that has not a corresponding pom.xml file supporting it, you may use the deploy-file target:
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
This allows you to deploy any kind of artifact from any origin into a maven repository, specifying by command line the group, artifact and version coordinates, and anything else you need.
In order to deploy it to the right place depending on your version, I can propose you this fragment of an ant script we built for a similar purpose:
<condition property="url" value="${snapshots.repo.url}" else="${releases.repo.url}">
<contains string="${project.version}" substring="-SNAPSHOT"/>
</condition>
<exec executable="cmd">
<arg value="/c"/>
<arg value="mvn.bat"/>
<arg value="deploy:deploy-file"/>
<arg value="-DgroupId=com.myorg.swagger"/>
<arg value="-DartifactId=swagger_file"/>
<arg value="-Dversion=${project.version}"/>
<arg value="-U"/>
<arg value="-Dfile=./mydir/my_swagger_file.json"/>
<arg value="-Durl=${url}"/>
<arg value="-DrepositoryId=my_repo_id"/>
</exec>
This will only work in Windows, but is easily adaptable for any other OS. The interesting bit here is the repositoryId, that should point to an existing authentication in your settings.xml:
...
<servers>
<server>
<id>my_repo_id</id>
<username>your_user_for_deployment</username>
<password>your_pwd_for_deployment</password>
</server>
</servers>
...
Hope this will help you ^^