Tomo Suzuki created BEAM-11827:
----------------------------------

             Summary: 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


[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).





--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to