Upload two artifact from only one project about bintray-release HOT 7 CLOSED

This is possible, we've done something similar internally.

Your modules need to be treated individually and your dependency version names shared

./gradlew module1:bintrayUpload
./gradlew module2:bintrayUpload

from bintray-release.

I found similar issue.
I have two modules (android library and apt processor) in one project. Then, android library was uploaded and published. However apt processor was uploaded but not published.

from bintray-release.

What is the behaviour you expect?
Each module is uploaded and has to be used as a separate dependency, you can't upload two modules and expect it to somehow zip them together and create 1 dependency that isn't how it works. Is this your thinking?

from bintray-release.

No. I expect two modules are uploaded to jcenter as two maven repos.
For example, my project with two modules have been uploaded to these repos.
https://bintray.com/kobakei/maven/spot/view
https://bintray.com/kobakei/maven/spot-compiler/view
But one module has not been published by the plugin.

from bintray-release.

@blundell I expect that after performing gradle bintrayUpload... have my two modules uploaded to bintray.

The result just now is that your plugin only uploads .jar and .aar files from my modules, but don't create neither upload any .pom related to those modules and then bintray doesn't allow them to be published.

I have my project with your plugin integration on this branch. You can see it and do some trails over it ;)

from bintray-release.

@kobakei
you can upload one module,and then another.
but it can't use like
compile 'com.yubaokang:intentinject-api:v1.0.0'
apt 'com.yubaokang:intentinject-compiler:v1.0.0'
it must use like
compile 'com.yubaokang:intentinject-api:v1.0.0'
compile 'com.yubaokang:intentinject-compiler:v1.0.0'
when i build apk ,the guava library will be builed in the apk.

from bintray-release.

tracking via: #16

from bintray-release.