Skip to content

Report on specific module in a multi-module project without normal compilation fails #112

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.

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

Closed
eyalroth opened this issue Sep 10, 2019 · 1 comment · Fixed by #113
Closed

Comments

@eyalroth
Copy link
Contributor

If one attempts to reportScoverage on a specific module in a multi-module project without normal compilation, the compilation will fail in case this specific module depends on another module in the project.

For instance, in a multi-module project, a module depends on common, trying to run the following will fail in compilation:
gradle :a:reportScoverage -x compileScala

The culprit is in the code which is supposed to make sure that the scoverage compilation output directory will be build/classes/scala/main instead of build/classes/scala/scoverage when normal compilation is omitted.

It only does this when the reportScoverage task is in the graph of that module; in the aforementioned example, the plugin will fail to detect that the (scoverage) compilation of the common module needs to adjust its output directory since the :common:reportScoverage task is not in the task graph.

eyalroth added a commit to eyalroth/gradle-scoverage that referenced this issue Sep 10, 2019
maiflai added a commit that referenced this issue Sep 14, 2019
…-normal-compile

Fix #112 - specific module in multi module project without normal compilation
@Mrfaisa6
Copy link

#112 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants