Modify maven_export to allow exporting zip archives#1368
Modify maven_export to allow exporting zip archives#1368shs96c merged 3 commits intobazel-contrib:masterfrom
Conversation
This enables publishing zip files to maven. The project I'm converting over to bazel publishes C++ artifacts (JNI and others) as zip files to maven. Signed-off-by: Austin Schuh <austin.linux@gmail.com>
|
Build failure looks like a flake |
|
Apologies for getting to this so late. Is there any reason why you wouldn't use the java_export(
name = "example-export",
classifier_artifacts = {
"zip": ":create-zip-archive",
},
maven_coordinates = "com.example:bazel-example:0.0.1",
) |
|
Unfortunately, This creates: vs the required If there's another way to do this, I'm all ears. The simplest way I could find was to make a new rule. |
|
I'd be okay if you made it possible for the jar and javadoc artifacts to be optional. It seems like a smaller change than a new rule.... |
Signed-off-by: Austin Schuh <austin.linux@gmail.com>
|
I'm not sure it ends up cleaner, but here you go. |
|
CI now passes. Looks like updating to the latest master made that work. What do you think? Any feedback? |
shs96c
left a comment
There was a problem hiding this comment.
LGTM. Thank you for the reworking.
* master: (39 commits) Fix resolution of Android/AAR artifacts with Gradle resolver (bazel-contrib#1395) fail_if_repin_required is now True by default and minor improvement to failure message (bazel-contrib#1397) Housekeeping before we release 6.8 (bazel-contrib#1384) Add dll, dylib and so types to maven package mappings (bazel-contrib#1392) [bzlmod] Allow suppressing warning about multiple contributing modules. (bazel-contrib#1393) Use the artifact default values when adding them to a struct and add tests for coursier artifacts that have empty versions provided by BOMs and don't inlcude them in outdated (bazel-contrib#1390) Allow package exclusions and inclusions in javadocs (bazel-contrib#1293) Document well-known issues with `bzlmod` (bazel-contrib#1388) Begin documenting the gradle resolver (bazel-contrib#1389) Run gradle regression tests in CI (bazel-contrib#1385) Modify maven_export to allow exporting zip archives (bazel-contrib#1368) Allow root module's override tags to take precedence over the overridees from transitive deps. (bazel-contrib#1381) Ensure root module artifacts and boms take precedence with warnings (bazel-contrib#1373) Update maven-metadata.xml when publishing locally (bazel-contrib#1369) Add support for gradle resolver (bazel-contrib#1357) Prepare for 6.8 release (bazel-contrib#1380) Remove the Windows `kt_jvm_export` example (bazel-contrib#1383) Avoid spurious warnings about poorly formatted artifact coordinates (bazel-contrib#1374) Flip `fail_if_repin_required` to `True` by default (bazel-contrib#1371) Allow the same coordinate to be overridden in different repos (bazel-contrib#1378) ...
This enables publishing zip files to maven. The project I'm converting over to bazel publishes C++ artifacts (JNI and others) as zip files to maven.