[
https://issues.apache.org/jira/browse/SAMZA-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976120#comment-13976120
]
Steve Yates commented on SAMZA-95:
----------------------------------
Guys to be honest i am struggling with this one. The coverage reports are a
great tool to have but if we are not using them their value will diminish
quickly. I guess i am struggling with gradle more than anything coming from a
pure maven background.
Would organisations looking to adopt or experiment with Samza look to coverage
reports reports as an indicator of maturity ?
> Gradle projectReport fails with jacocoTestReport issue
> ------------------------------------------------------
>
> Key: SAMZA-95
> URL: https://issues.apache.org/jira/browse/SAMZA-95
> Project: Samza
> Issue Type: Bug
> Components: build
> Reporter: Jakob Homan
> Assignee: Steve Yates
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: SAMZA-95-3.diff, SAMZA-95-4.diff, SAMZA-95.diff,
> SAMZA-95.diff
>
>
> {noformat}[jhoman@jhoman-ld samza]$ ./gradlew projectReport
> The TaskContainer.add() method has been deprecated and is scheduled to be
> removed in Gradle 2.0. Please use the create() method instead.
> :samza-api:dependencyReport UP-TO-DATE
> :samza-api:propertyReport UP-TO-DATE
> :samza-api:taskReport
> :samza-api:projectReport
> :samza-core_2.9.2:dependencyReport
> :samza-core_2.9.2:propertyReport
> :samza-core_2.9.2:taskReport FAILED
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':samza-core_2.9.2:taskReport'.
> > Could not determine the dependencies of task
> > ':samza-core_2.9.2:jacocoTestReport'.
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> BUILD FAILED{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
