Investigate multimodule projects about bintray-release HOT 7 CLOSED

I've done it in #153 .
In this way you can include a module into your aar.

But as in SO mentioned that is not the default and not typical for the java world.
Beside of that this issue have nothing todo with the bintray-release directly.
You can simply use the plugin and put another module into the aar/jar like I've done in #153.

I don't know what the plugin should do here?
I think it is not the responsibility of the plugin to define which other modules should be included in the aar/jar...

What i wouldn't want - having to add the plugin to each module and configure separately EWW

I think that is "another" topic.
The plugin should not be responsible to take care of putting module into a aar/jar.
But I think we could provide a better API for such cases.
Thinking about of having a top-level build.gradle with:

basePublish {
    userOrg = 'novoda'
    groupId = 'novoda.multi.module'
    publishVersion = "1"
//    artifactId = 'thirtyinch'
    uploadName = 'MultiModuleSample'
    description = 'a Model View Presenter library for Android'
    website = 'https://github.com/novodoa/multimodule'
}

and in each module build.gradle then just

publish {
    artifactId = 'module1' // module2, module3 etc.
}

I will close that and create another issue with that idea...

from bintray-release.

What I would want is - the plugin is added to the module that contains the public api. It would then find source code in other modules and merge it into this one. Thus when released it's not multimodule but only one.

from bintray-release.

What i wouldn't want - having to add the plugin to each module and configure separately EWW

from bintray-release.

Some background info http://stackoverflow.com/questions/26939628/gradle-mavendeployer-how-to-include-a-separate-modules-code

from bintray-release.

I was under the impression that compile project(:'foo') would pull all the .class into the local build dir hmm

from bintray-release.

same but apparently it doesn't it makes a transitive dependency like in that SO question :-(

from bintray-release.

Something to investigate then

from bintray-release.