Instances of dependency on self

I'm working on a POC in my new role for Bazel and I have encountered instances in the `maven_install.json` where an entry has a dependency on itself. I have eyeballed the POM files as well as The BUILD file in the `@maven` workspace and I cannot see a cycle.

I haven't spend much time looking at how these rules work but I believe `jvm_import` is taking the depset data from the `maven_install.json` file into consideration ?

Would it be possible to filter out dependencies on self before the json file is written ?

Start by tracing how dependencies are written to maven_install.json, then compare the POM files with the BUILD file in the @maven workspace and inspect how jvm_import consumes the depset data. Done means the generated JSON no longer contains an artifact depending on itself while the corresponding Maven workspace remains valid.

Written by the indexing model from the issue text.