Thank you for making this amazing ecosystem!
elemental2 depends on the gwt project as an http_archive (
|
name = "org_gwtproject_gwt", |
) for the GWT array stamper (used here
|
.setInvocationTarget(new TypeQualifier(ARRAY_STAMPER.getReference(false))) |
pulled from
|
"@org_gwtproject_gwt//user:super/com/google/gwt/emul/javaemul/internal/ArrayStamper.java", |
)
However, as of Bazel 9, the gwt repo needs some additional build rules. I made a gwt repo PR in gwtproject/gwt#10349 but the maintainer doesn't seem inclined to accept the patch. Do you have any thoughts on how to get this fixed? Whether getting that patch committed or forking the code into elemental2 like the gwt maintainer seems to be expecting?
In the meantime I've been patching elemental2 in my root MODULE.bazel but it feels bad: https://github.com/aschleck/trailcatalog/blob/main/MODULE.bazel#L33
Thank you for making this amazing ecosystem!
elemental2 depends on the gwt project as an http_archive (
elemental2/MODULE.bazel
Line 54 in 59747da
elemental2/java/elemental2/core/BuiltInClosureTypeCleaner.java
Line 204 in 59747da
elemental2/third_party/BUILD
Line 327 in 59747da
However, as of Bazel 9, the gwt repo needs some additional build rules. I made a gwt repo PR in gwtproject/gwt#10349 but the maintainer doesn't seem inclined to accept the patch. Do you have any thoughts on how to get this fixed? Whether getting that patch committed or forking the code into elemental2 like the gwt maintainer seems to be expecting?
In the meantime I've been patching elemental2 in my root MODULE.bazel but it feels bad: https://github.com/aschleck/trailcatalog/blob/main/MODULE.bazel#L33