[
https://issues.apache.org/jira/browse/KUDU-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17985925#comment-17985925
]
ASF subversion and git services commented on KUDU-3657:
-------------------------------------------------------
Commit bc852ca38327361e359427e5c5360a29359b1b27 in kudu's branch
refs/heads/branch-1.18.x from zchovan
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=bc852ca38 ]
[java] KUDU-3657: fix publishing
The changes introduced in KUDU-3610 have fixed the POM generation for
the kudu-hive java module, however the publishing for other modules were
broken as a side-effect. This patch aims to fix these issues.
The change in publishing.gradle file checks if the implementation and shadow
configurations are present to calculate the correct pom to be generated.
If they are not present for the given module, they are simply filled out
as empty arrays.
Additionally, the skipping of publishing wasn't working, this needed to
be fixed for the following modules (to keep in alignment with pre-gradle
upgrade behaviour):
* kudu-backup-common
* kudu-jepsen
* kudu-proto
* kudu-subprocess
Fixed the generated jar names of the following modules:
* kudu-backup -> kudu-backup3_2.12
* kudu-spark -> kudu-spark3_2.12
* kudu-spark-tools -> kudu-spark3-tools_2.12
Changed the compileUnshaded configuration to be extending the
compileOnly configuration. This was necessary to correct the scope of
these dependencies. This change also made it necessary to add the
compileUnshaded dependencies explicitly to the test compile path as
well[0].
[0] https://blog.gradle.org/introducing-compile-only-dependencies
Change-Id: Ie045805a68bfcd16325e1e4dbb38653cefe3a4b0
Reviewed-on: http://gerrit.cloudera.org:8080/22768
Reviewed-by: Abhishek Chennaka <[email protected]>
Tested-by: Alexey Serbin <[email protected]>
Reviewed-by: Alexey Serbin <[email protected]>
(cherry picked from commit 6d72d4a242076468501f3430b9a2cd050c634be2)
Reviewed-on: http://gerrit.cloudera.org:8080/23079
Reviewed-by: Marton Greber <[email protected]>
Tested-by: Marton Greber <[email protected]>
> KUDU-3610 broke Java publishing
> -------------------------------
>
> Key: KUDU-3657
> URL: https://issues.apache.org/jira/browse/KUDU-3657
> Project: Kudu
> Issue Type: Bug
> Components: java
> Reporter: Zoltan Chovan
> Assignee: Zoltan Chovan
> Priority: Critical
> Labels: build, java
>
> KUDU-3610 (Merged as 9befb11) has fixed the POM generation, however it seems
> to have broken the artifact publishing.
> When running the `publishToMavenLocal` task, it fails with the following
> error:
> {code:java}
> ./gradlew publishToMavenLocal
> > Task :kudu-jepsen:generatePomFileForMavenPublication FAILED
> > Task :kudu-subprocess:generatePomFileForMavenPublication FAILED
> > Task :kudu-hive:generatePomFileForMavenPublication FAILED
> > Task :kudu-test-utils:generatePomFileForMavenPublication FAILED
> > Task :kudu-spark-tools:generatePomFileForMavenPublication FAILED
> > Task :kudu-backup:generatePomFileForMavenPublication FAILEDFAILURE: Build
> > completed with 6 failures.1: Task failed with an exception.
> -----------
> * Where:
> Script '/Users/zchovan/CLionProjects/kudu/java/gradle/publishing.gradle'
> line: 74* What went wrong:
> Execution failed for task ':kudu-jepsen:generatePomFileForMavenPublication'.
> > Could not apply withXml() to generated POM
> > Could not get unknown property 'api' for configuration container of type
> org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.*
> Try:
> > Run with --stacktrace option to get the stack trace.
> > Run with --info or --debug option to get more log output.
> > Run with --scan to get full insights.
> ==============================================================================
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
