Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Multi-project Builds #50

Closed
rpmoore opened this issue Oct 15, 2014 · 5 comments
Closed

Multi-project Builds #50

rpmoore opened this issue Oct 15, 2014 · 5 comments

Comments

@rpmoore
Copy link

rpmoore commented Oct 15, 2014

Could you please add some examples of configuring the plugin for a multiproject build. I've been playing around with it and I've not been able to successfully configure the source sets so that my subproject source files are recognized by the plugin.

Thanks!
@shevek
Copy link

shevek commented Nov 6, 2014

+1

I have a multiproject build and I would like a single license report cuvering all submodules. There is no one "root" module which depends on all others which I can use in this place.

@hierynomus
Copy link
Owner

Could be as simple as:

allprojects {
  apply plugin: "license"
}

If you just want to apply the plugin to each project.

@sschuberth
Copy link
Contributor

I can confirm that using allprojects works, so I guess this can be closed. However, this will lead to individual reports per project, not a single report, but that's a different issue.

@shevek
Copy link

shevek commented Sep 8, 2015

I agree that allprojects{} works, this issue can be closed, and that #40 is my requirement.

@hierynomus
Copy link
Owner

#40 is fixed by @jonathannaguin. Closing this one now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@hierynomus @sschuberth @shevek @rpmoore