Create dagger-gwt artifact with bazel
See original GitHub issueSince Dagger 2.9 I get this error when compiling GWT:
Tracing compile failure path for type 'dagger.super.javax.inject.package-info'
[ERROR] Errors in 'jar:file:/work/.m2/repository/com/google/dagger/dagger-gwt/2.9/dagger-gwt-2.9.jar!/dagger/super/javax/inject/package-info.java'
[ERROR] Line 155: The declared package "javax.inject" does not match the expected package "dagger.super.javax.inject"
Tracing compile failure path for type 'dagger.super.javax.inject.Qualifier'
[ERROR] Errors in 'jar:file:/work/.m2/repository/com/google/dagger/dagger-gwt/2.9/dagger-gwt-2.9.jar!/dagger/super/javax/inject/Qualifier.java'
[ERROR] Line 17: The declared package "javax.inject" does not match the expected package "dagger.super.javax.inject"
Tracing compile failure path for type 'dagger.super.javax.inject.Inject'
[ERROR] Errors in 'jar:file:/work/.m2/repository/com/google/dagger/dagger-gwt/2.9/dagger-gwt-2.9.jar!/dagger/super/javax/inject/Inject.java'
[ERROR] Line 17: The declared package "javax.inject" does not match the expected package "dagger.super.javax.inject"
Tracing compile failure path for type 'dagger.super.javax.inject.Provider'
[ERROR] Errors in 'jar:file:/work/.m2/repository/com/google/dagger/dagger-gwt/2.9/dagger-gwt-2.9.jar!/dagger/super/javax/inject/Provider.java'
[ERROR] Line 17: The declared package "javax.inject" does not match the expected package "dagger.super.javax.inject"
Tracing compile failure path for type 'dagger.super.javax.inject.Scope'
[ERROR] Errors in 'jar:file:/work/.m2/repository/com/google/dagger/dagger-gwt/2.9/dagger-gwt-2.9.jar!/dagger/super/javax/inject/Scope.java'
[ERROR] Line 17: The declared package "javax.inject" does not match the expected package "dagger.super.javax.inject"
Tracing compile failure path for type 'dagger.super.javax.inject.Named'
[ERROR] Errors in 'jar:file:/work/.m2/repository/com/google/dagger/dagger-gwt/2.9/dagger-gwt-2.9.jar!/dagger/super/javax/inject/Named.java'
[ERROR] Line 17: The declared package "javax.inject" does not match the expected package "dagger.super.javax.inject"
Tracing compile failure path for type 'dagger.super.javax.inject.Singleton'
[ERROR] Errors in 'jar:file:/work/.m2/repository/com/google/dagger/dagger-gwt/2.9/dagger-gwt-2.9.jar!/dagger/super/javax/inject/Singleton.java'
[ERROR] Line 17: The declared package "javax.inject" does not match the expected package "dagger.super.javax.inject"
[ERROR] Aborting compile due to errors in some input files
Issue Analytics
- State:
- Created 7 years ago
- Comments:13
Top Results From Across the Web
Artifact-Based Build Systems | Bazel
This page covers artifact-based build systems and the philosophy behind their creation. Bazel is an artifact-based build system. While task-based build systems ...
Read more >How to publish artifacts from Bazel to Maven Central - Medium
First, Bazel does not publish build output jars in a local/remote maven repository by default. A separate publishing ruleset is needed.
Read more >How to package and deploy build output and artifacts - YouTube
0:00 Intro2:55 Setup and Compile python 8:11 Packaging to a zip file12:36 Find the artifact path14:57 Writing a deployment script# bazel In ...
Read more >BUILD.bazel - platform/tools/base - Git at Google
This Maven repository contains artifacts that are built by Bazel, but also needed by. # AGP build. The AGP build uses this repo...
Read more >How do you aggregate Bazel build artifacts together that have ...
This can be a little involved, depending on exactly what you need to do. What you need here is a Starlark rule that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That’s fixed in #726. There’ll be a snapshot once that’s merged (and travis builds)
This is now fixed