Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

org.gwtproject.dom:gwt-dom:1.0.0-RC1 is not usable from J2CL #127

Open
niloc132 opened this issue Mar 1, 2022 · 0 comments
Open

org.gwtproject.dom:gwt-dom:1.0.0-RC1 is not usable from J2CL #127

niloc132 opened this issue Mar 1, 2022 · 0 comments
Labels
Milestone

Comments

@niloc132
Copy link
Member

niloc132 commented Mar 1, 2022

Once 1.0.0-RC2 is released (and downstream projects such as gwt-animation, -aria, -layout, -event-dom), we can update the gwt-modules-project integration test to restore testing on it, and get better guarantees about the state of the ecosystem.

@niloc132 niloc132 added this to the 0.20 milestone Mar 1, 2022
niloc132 added a commit to niloc132/j2clmavenplugin that referenced this issue Mar 1, 2022
Gradle's "implementation" configuration for dependencies results in
published maven poms that are technically accurate for building
bytecode, but useless for building J2CL. To fix this, we interpret any
scope=runtime as if it says scope=compile.

This patch also tests many publicly released gwt modules to ensure that
they build cleanly in the plugin, with the hope of avoiding this issue
in the future. There are several commented out dependencies, to avoid
trying to build gwt-dom until the next release is ready. Bug Vertispan#127 is
filed for followup.

Fixes Vertispan#126
niloc132 added a commit to niloc132/j2clmavenplugin that referenced this issue Mar 1, 2022
Gradle's "implementation" configuration for dependencies results in
published maven poms that are technically accurate for building
bytecode, but useless for building J2CL. To fix this, we interpret any
scope=runtime as if it says scope=compile.

This patch also tests many publicly released gwt modules to ensure that
they build cleanly in the plugin, with the hope of avoiding this issue
in the future. There are several commented out dependencies, to avoid
trying to build gwt-dom until the next release is ready. Bug Vertispan#127 is
filed for followup.

Fixes Vertispan#126
@niloc132 niloc132 added the tests label Mar 3, 2022
@niloc132 niloc132 modified the milestones: 0.20, 0.21 Jul 14, 2022
niloc132 added a commit to niloc132/j2clmavenplugin that referenced this issue Jul 14, 2022
Gradle's "implementation" configuration for dependencies results in
published maven poms that are technically accurate for building
bytecode, but useless for building J2CL. To fix this, we interpret any
scope=runtime as if it says scope=compile.

This patch also tests many publicly released gwt modules to ensure that
they build cleanly in the plugin, with the hope of avoiding this issue
in the future. There are several commented out dependencies, to avoid
trying to build gwt-dom until the next release is ready. Bug Vertispan#127 is
filed for followup.

Fixes Vertispan#126
niloc132 added a commit to niloc132/j2clmavenplugin that referenced this issue Nov 8, 2022
Gradle's "implementation" configuration for dependencies results in
published maven poms that are technically accurate for building
bytecode, but useless for building J2CL. To fix this, we interpret any
scope=runtime as if it says scope=compile.

This patch also tests many publicly released gwt modules to ensure that
they build cleanly in the plugin, with the hope of avoiding this issue
in the future. There are several commented out dependencies, to avoid
trying to build gwt-dom until the next release is ready. Bug Vertispan#127 is
filed for followup.

Fixes Vertispan#126
@niloc132 niloc132 modified the milestones: 0.21, 0.23 Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant