Custom Java navigation policy that allows non-Maven source JAR layout

Open vmax opened this issue 6 years ago • 4 comments

Checklist

[X] I have filed an issue about this change and discussed potential changes with the maintainers.
[ ] I have received the approval from the maintainers to make this change.
[X] This is not a stylistic, refactoring, or cleanup change.

Discussion thread for this change

Issue number: #1206

Description of this change

Implement a custom Java navigation policy which accounts for source JARs that don't follow the Maven structure (see linked issue for example)

Sep 26 '19 11:09 vmax

Any updates on the revision status of this PR, @bazelbuild team? We really need this fix in the plugin to actually leverage the package flexilbility that Bazel offers. @bazelbuild-intellij @vsiva @chaoren @brendandouglas

Oct 11 '19 13:10 haikalpribadi

Hi :) Checking in on this PR again ...

Any updates on the revision status of this PR, @bazelbuild team? We really need this fix in the plugin to actually leverage the package flexibility that Bazel offers. @bazelbuild-intellij @vsiva @chaoren @brendandouglas

Jan 17 '20 15:01 haikalpribadi

Hi @bazelbuild-intellij team. Can you share some reason as to why this PR can't get merged? We're happy to fix any issues you find with it! :)

Apr 16 '20 16:04 haikalpribadi

Hi, @bazelbuild-intellij @vsiva @chaoren @brendandouglas - would you mind sharing why this PR still can't be merged? We're happy to make any changes if needed! Thank you!

May 11 '20 16:05 haikalpribadi