{"action":"created","issue":{"url":"https://api.github.com/repos/bintray/gradle-bintray-plugin/issues/104","repository_url":"https://api.github.com/repos/bintray/gradle-bintray-plugin","labels_url":"https://api.github.com/repos/bintray/gradle-bintray-plugin/issues/104/labels{/name}","comments_url":"https://api.github.com/repos/bintray/gradle-bintray-plugin/issues/104/comments","events_url":"https://api.github.com/repos/bintray/gradle-bintray-plugin/issues/104/events","html_url":"https://github.com/bintray/gradle-bintray-plugin/issues/104","id":129606617,"number":104,"title":"Feature Request: Make bintray closure a little more \"lazy\"","user":{"login":"dljsjr","id":444635,"avatar_url":"https://avatars.githubusercontent.com/u/444635?v=3","gravatar_id":"","url":"https://api.github.com/users/dljsjr","html_url":"https://github.com/dljsjr","followers_url":"https://api.github.com/users/dljsjr/followers","following_url":"https://api.github.com/users/dljsjr/following{/other_user}","gists_url":"https://api.github.com/users/dljsjr/gists{/gist_id}","starred_url":"https://api.github.com/users/dljsjr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dljsjr/subscriptions","organizations_url":"https://api.github.com/users/dljsjr/orgs","repos_url":"https://api.github.com/users/dljsjr/repos","events_url":"https://api.github.com/users/dljsjr/events{/privacy}","received_events_url":"https://api.github.com/users/dljsjr/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-01-28T22:43:52Z","updated_at":"2016-09-22T06:55:04Z","closed_at":null,"body":"I'm not sure what the best title for this issue is, but hopefully this description captures what I'm looking for. Feel free to close it if it's too vague.\r\n\r\nI work with a large Gradle multi-project build that configures a Maven publication for all of its subprojects. Almost all of the Maven publication logic is the same between projects minus a few things that can be encapsulated here and there in variables, and so I am able to configure the Maven publication setup by using `subprojects(Closure)` in the root project. As an example, the subprojects have mixed licenses; some are Apache, some are GPL. When I build up the POM nodes in `pom.withXml`, I can refer to project extensions that don't exist on the root project but that do exist on the subproject, and this is fine.\r\n\r\nI'd really like to be able to configure the bintray uploads the same way instead of having to write an identical bintray closure for every subproject just to change stuff like the license and the name, but it appears that the bintray closure is super greedy in evaluating things in that my builds fail if I try to use the same project extensions I use in the Maven publications, saying that they don't exist on the root project.\r\n\r\nI'm definitely not a Gradle expert or a Gradle plugin expert so I could very well just be doing something silly, but hopefully this makes sense. I'll see if I can't put together a very simple self-contained example and then I'll come back with something a bit more concrete, hopefully."},"comment":{"url":"https://api.github.com/repos/bintray/gradle-bintray-plugin/issues/comments/248826766","html_url":"https://github.com/bintray/gradle-bintray-plugin/issues/104#issuecomment-248826766","issue_url":"https://api.github.com/repos/bintray/gradle-bintray-plugin/issues/104","id":248826766,"user":{"login":"paour","id":90963,"avatar_url":"https://avatars.githubusercontent.com/u/90963?v=3","gravatar_id":"","url":"https://api.github.com/users/paour","html_url":"https://github.com/paour","followers_url":"https://api.github.com/users/paour/followers","following_url":"https://api.github.com/users/paour/following{/other_user}","gists_url":"https://api.github.com/users/paour/gists{/gist_id}","starred_url":"https://api.github.com/users/paour/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/paour/subscriptions","organizations_url":"https://api.github.com/users/paour/orgs","repos_url":"https://api.github.com/users/paour/repos","events_url":"https://api.github.com/users/paour/events{/privacy}","received_events_url":"https://api.github.com/users/paour/received_events","type":"User","site_admin":false},"created_at":"2016-09-22T06:55:04Z","updated_at":"2016-09-22T06:55:04Z","body":"It would be real nice if this plugin were able to evaluate its closure when it needs to, rather than during the configuration phase. It would make it possible to at least use the list of tasks to set some of the values."}}
{"actor":{"display_login":"paour"}}