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

Deps to Android support libraries does not show up as external libraries of the project #103

Closed
likan999 opened this issue Jun 16, 2017 · 1 comment

Comments

@likan999
Copy link

likan999 commented Jun 16, 2017

If my android project has deps to Android support libraries, then after import/sync in Android Studio, the support libraries are not shown up as external libraries, therefore in the Java editor their classes will be shown as "Cannot resolve symbol".

To reproduce, just clone the official tutorial https://github.com/bazelbuild/examples.git and "git am" the attached patch, and import the WORKSPACE under "tutorial/" directory, and BUILD file under "tutorial/android/". Note the minSdk and api_level in the patch are not necessary, I have them just because I don't have lower versions of sdk installed.

The OS is Mac OSX.

diff.txt

@likan999 likan999 changed the title Symbols from support libraries is not resolved Deps to Android support libraries does not show up as external libraries of the project Jun 23, 2017
@jvoung
Copy link

jvoung commented Apr 5, 2018

Should be handled now in the plugin (I tried the diff.txt + example on plugin version 2018.03.12.0.6)

Support libraries used aar_import, and the basics of aar_import now work (https://github.com/bazelbuild/intellij/blob/983a509e55b78aaa5323adc9e2742db783d90d57/aswb/src/com/google/idea/blaze/android/sync/model/AarLibrary.java, and related code)

@jvoung jvoung closed this as completed Apr 5, 2018
blorente pushed a commit to blorente/intellij that referenced this issue Oct 3, 2023
feat: Add commented-out gazelle target to default project view (bazelbuild#104)

feat(release): Publish IntelliJ CE version of the plugin. (bazelbuild#103)

feat(tools): Add script to check versions (bazelbuild#105)

Radar: rdar://110389652 (Opening section of Bazel plugin setup confusing.)

Co-authored-by: Daniel Wagner-Hall <dwagnerhall@apple.com>

build: Add release pipeline for version checker (bazelbuild#109)

Co-authored-by: Gibson Fahnestock <gib@apple.com>
blorente pushed a commit to blorente/intellij that referenced this issue Oct 24, 2023
feat: Add commented-out gazelle target to default project view (bazelbuild#104)

feat(release): Publish IntelliJ CE version of the plugin. (bazelbuild#103)

feat(tools): Add script to check versions (bazelbuild#105)

Radar: rdar://110389652 (Opening section of Bazel plugin setup confusing.)

Co-authored-by: Daniel Wagner-Hall <dwagnerhall@apple.com>

build: Add release pipeline for version checker (bazelbuild#109)

Co-authored-by: Gibson Fahnestock <gib@apple.com>

feat: capture sdk and bazel plugin info for radar (bazelbuild#117)

* feat: capture sdk and bazel plugin info for radar

* Fix issues for clion plugin version

Co-authored-by: Joshua Harris <jharris33@apple.com>

build(prb): Make prb test every version of released products

build(ci): Increase timeout in Rio

build(ci): Key version counters by product

build(ci): Make apple version checker publish optional

fix: Default to workspace to infer project name (bazelbuild#122)

Instead of defaulting to "the parent directory of the project view
file", which is rarely what we want.

feat: Add support for cc_gtest_testsuite in BUILD files (bazelbuild#121)
blorente pushed a commit to blorente/intellij that referenced this issue Nov 1, 2023
feat: Add commented-out gazelle target to default project view (bazelbuild#104)

feat(release): Publish IntelliJ CE version of the plugin. (bazelbuild#103)

feat(tools): Add script to check versions (bazelbuild#105)

Radar: rdar://110389652 (Opening section of Bazel plugin setup confusing.)

Co-authored-by: Daniel Wagner-Hall <dwagnerhall@apple.com>

build: Add release pipeline for version checker (bazelbuild#109)

Co-authored-by: Gibson Fahnestock <gib@apple.com>

feat: capture sdk and bazel plugin info for radar (bazelbuild#117)

* feat: capture sdk and bazel plugin info for radar

* Fix issues for clion plugin version

Co-authored-by: Joshua Harris <jharris33@apple.com>

build(prb): Make prb test every version of released products

build(ci): Increase timeout in Rio

build(ci): Key version counters by product

build(ci): Make apple version checker publish optional

fix: Default to workspace to infer project name (bazelbuild#122)

Instead of defaulting to "the parent directory of the project view
file", which is rarely what we want.

feat: Add support for cc_gtest_testsuite in BUILD files (bazelbuild#121)

cleanup: Enable --test_output=errors by default
blorente pushed a commit to blorente/intellij that referenced this issue Jan 30, 2024
docs(readme): Reformat readme, change rebase process
feat: Add commented-out gazelle target to default project view (bazelbuild#104)

feat(release): Publish IntelliJ CE version of the plugin. (bazelbuild#103)

feat(tools): Add script to check versions (bazelbuild#105)

Radar: rdar://110389652 (Opening section of Bazel plugin setup confusing.)

Co-authored-by: Daniel Wagner-Hall <dwagnerhall@apple.com>

build: Add release pipeline for version checker (bazelbuild#109)

Co-authored-by: Gibson Fahnestock <gib@apple.com>

feat: capture sdk and bazel plugin info for radar (bazelbuild#117)

* feat: capture sdk and bazel plugin info for radar

* Fix issues for clion plugin version

Co-authored-by: Joshua Harris <jharris33@apple.com>

build(prb): Make prb test every version of released products

build(ci): Increase timeout in Rio

build(ci): Key version counters by product

build(ci): Make apple version checker publish optional

fix: Default to workspace to infer project name (bazelbuild#122)

Instead of defaulting to "the parent directory of the project view
file", which is rarely what we want.

feat: Add support for cc_gtest_testsuite in BUILD files (bazelbuild#121)

cleanup: Enable --test_output=errors by default

feat(file-a-radar): add IntelliJ log to File a Radar draft

Turns out to be surprisingly easy to attach IntelliJ logs to the created
radar draft.

rdar://117680933 ([IDE] Capture IntelliJ log when Filing a Radar)

docs: Rewrite release instructions (bazelbuild#155)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants