Skip to content

Do not use the default namespace for the maven.install tag #672

@shs96c

Description

@shs96c

Using the default maven namespace causes pollution for projects that depend on rules_closure. I'm attempting to use rules_closure with Selenium itself, and introducing the ruleset has lead to the unusual condition that we now depend on our own published jars.

In rules_jvm_external we advise against rulesets included via bazel_dep from using the default namespace (in this section) Perhaps closure_deps could be used instead?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions