[ 
https://issues.apache.org/jira/browse/BEAM-11827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anonymous updated BEAM-11827:
-----------------------------
    Status: Triage Needed  (was: Resolved)

> Gradle task :checkJavaLinkage is not working
> --------------------------------------------
>
>                 Key: BEAM-11827
>                 URL: https://issues.apache.org/jira/browse/BEAM-11827
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>            Reporter: Tomo Suzuki
>            Assignee: Tomo Suzuki
>            Priority: P2
>             Fix For: Not applicable
>
>         Attachments: Screen Shot 2021-02-17 at 13.55.35.png
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> [https://github.com/apache/beam/pull/13994] revealed that the 
> :checkJavaLinkage task in the root Gradle file does not generate the expected 
> file.
>   
> {noformat}
> suztomo@suztomo:~/beam$ ./gradlew -Ppublishing -PskipCheckerFramework 
> -PjavaLinkageArtifactIds=beam-sdks-java-io-google-cloud-platform 
> -PjavaLinkageWriteBaseline=build/linkagecheck/baseline-beam-sdks-java-io-google-cloud-platform.xml
>  :checkJavaLinkage
> Configuration on demand is an incubating feature.
> > Task :checkJavaLinkage
> NOTE: This task published artifacts into your local Maven repository. You may 
> want to remove them manually.
> Deprecated Gradle features were used in this build, making it incompatible 
> with Gradle 7.0.
> Use '--warning-mode all' to show the individual deprecation warnings.
> See 
> https://docs.gradle.org/6.8/userguide/command_line_interface.html#sec:command_line_warnings
> BUILD SUCCESSFUL in 51s
> 1115 actionable tasks: 201 executed, 914 up-to-date
> suztomo@suztomo:~/beam$ 
> suztomo@suztomo:~/beam$ ls 
> build/linkagecheck/baseline-beam-sdks-java-io-google-cloud-platform.xml
> ls: cannot access 
> 'build/linkagecheck/baseline-beam-sdks-java-io-google-cloud-platform.xml': No 
> such file or directory
> {noformat}
> It's as if the 
> "com.google.cloud.tools.opensource.classpath.LinkageCheckerMain" is not 
> called at all while it does resolve the Gradle task dependencies (such as 
> publishMavenJavaPublicationToMavenLocal).
> h1. How to attach Java debugger to checkJavaLinkage task
> In MacBook, I was able to produce the problem. The checkJavaLinkage task does 
> not generate the expected file.
> {noformat}
> ./gradlew  --stacktrace -Ppublishing -PskipCheckerFramework \
>   -PjavaLinkageArtifactIds=beam-sdks-java-io-google-cloud-platform \
>   
> -PjavaLinkageWriteBaseline=build/linkagecheck/baseline-beam-sdks-java-io-google-cloud-platform.xml
>  \
>   :checkJavaLinkage --debug-jvm
> {noformat}
> I found that the build.gradle.kts passes garbage to LinkageCheckerMain class.
> !Screen Shot 2021-02-17 at 13.55.35.png|width=688,height=458!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to