tree 015ccfe04b52411dc15f3a05e8a05cd6b7434491
parent 5377ba4d5c7478f164ec6c873e89cbc8429d553a
author Jin <jin@users.noreply.github.com> 1563547475 -0700
committer Copybara-Service <copybara-worker@google.com> 1563547558 -0700

Augment recommendation in java_import_external to be consistent with maven_jar, rules_jvm_external naming style

maven_jar recommends the following:

> Note that the maven_jar name is used as a repository name, so it is limited by the rules governing workspace names: it cannot contain dashes nor dots (see the documentation on workspace names for the exact specification). By convention, maven_jar names should match the artifact name, replacing illegal characters with underscores and leaving off the version. For example, a rule with artifact = "org.apache.commons:commons-lang3:3.4" should have name = "org_apache_commons_commons_lang3".

https://docs.bazel.build/versions/master/be/workspace.html#maven_jar_name

`rules_jvm_external` follows the same algorithm and generates the following for `com.google.guava:guava`:

```
@maven//:com_google_guava_guava

# with maven_install.generate_compat_repositories
@com_google_guava_guava//jar
@com_google_guava_guava//:com_google_guava_guava # or @com_google_guava_guava
```

This PR sets the recommendation in `java_import_external` to be aligned with `maven_jar` and `rules_jvm_external` to improve interoperability and lower migration friction.

Related: https://github.com/bazelbuild/bazel/issues/8908

Closes #8929.

PiperOrigin-RevId: 258965649