Oleksii

What if `whl` would be allowed if some platform type is specified via plugin properties? So when there is no `sdist` artifact `whl` could be used directly.

I'm currently working on importer module. So that will be OK if I'll convert it to java in a separate PR?

@zvezdan what do you think?

Created pull request for twine `ivy` extension https://github.com/pypa/twine/pull/300. Even if it would be rejected, you can still get my patch there

@kopy07 Is this worth another pull request? I mean new plugin for nexus support

Working on upload task for it now. Will try to migrate to java.

@shvilime Nexus supports all kinds of repositories. The goal was to use existing Nexus instead of deploying additional artifactory instance.

@shvilime Existing means the one I already use for Npm, Maven and Pypi. As for ivy - gradle allows to define repo url pattern, ivy is one of supported for...

Nope. I've patched pivy-importer to generate all the ivy metadata for my dep tree and twine to upload whole local pypi-ivy repo to Nexus.

@shvilime please, read "solutions" section of my original post. I've patched twine to upload ivy files within regular sdists and taught gradle plugin to use pypi-ivy metadata similar to how...