{"action":"closed","issue":{"url":"https://api.github.com/repos/kellymclaughlin/rebar3-tidy-deps-plugin/issues/1","labels_url":"https://api.github.com/repos/kellymclaughlin/rebar3-tidy-deps-plugin/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/kellymclaughlin/rebar3-tidy-deps-plugin/issues/1/comments","events_url":"https://api.github.com/repos/kellymclaughlin/rebar3-tidy-deps-plugin/issues/1/events","html_url":"https://github.com/kellymclaughlin/rebar3-tidy-deps-plugin/issues/1","id":66356558,"number":1,"title":"Use in a dependency","user":{"login":"tsloughter","id":36227,"avatar_url":"https://avatars.githubusercontent.com/u/36227?v=3","gravatar_id":"","url":"https://api.github.com/users/tsloughter","html_url":"https://github.com/tsloughter","followers_url":"https://api.github.com/users/tsloughter/followers","following_url":"https://api.github.com/users/tsloughter/following{/other_user}","gists_url":"https://api.github.com/users/tsloughter/gists{/gist_id}","starred_url":"https://api.github.com/users/tsloughter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tsloughter/subscriptions","organizations_url":"https://api.github.com/users/tsloughter/orgs","repos_url":"https://api.github.com/users/tsloughter/repos","events_url":"https://api.github.com/users/tsloughter/events{/privacy}","received_events_url":"https://api.github.com/users/tsloughter/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-04T19:29:30Z","updated_at":"2015-04-09T22:13:33Z","closed_at":"2015-04-09T22:13:33Z","body":"Working on changes to how hooks work, https://github.com/rebar/rebar3/pull/316, I realized that this plugin shouldn't work even for the current way rebar3/master works if it is to be used by a dependency of a project. It would only work at the top level.\r\n\r\nIn trying to resolve this I realized maybe a better solution would be to have this plugin be instead of a provider a custom resource. Meaning it would look like:\r\n\r\n```\r\n{lager, {github, \"basho/lager.git\", {tag, \"2.1.1\"}}},\r\n```\r\n\r\nIt'll require a few changes on the rebar3 side and it would basically be able to just call over to `rebar_git_resource` after updating the source, but it would be a better solution.\r\n\r\nWhat do you think? I can start on the rebar3 changes to allow plugins to provide resource behaviour implementations today.\r\n"}}