Open alfredomusumeci opened 2 years ago
I found a quick solution to this while waiting for an official fix:
Add the following:
override_targets = {
"com_atlassian_commonmark_commonmark" : "org_commonmark_commonmark",
}
to the maven_install code, under the artifacts list.
Hi, I just stumbled across this exact same issue today. Was the underlying cause ever found?
The override_targets workaround works for me for now
Hello,
I spotted a problem when adding a specific dependency to the WORKSPACE file, whose settings are shown below.
What happens is that when adding the "io.swagger:codegen.v3:swagger-codegen:3.0.32" (and all other swagger dependencies) the following error is thrown: Error:(793, 11) in deps attribute of jvm_import rule @maven//:io_swagger_swagger_codegen: rule '@maven//:com_atlassian_commonmark_commonmark' does not exist
This is because the target "@maven//:com_atlassian_commonmark_commonmark" is never created - instead what is created is an apparently similar package called "org_commonmark_commonmark". If I add an alias to the maven/BUILD file like so
the problem seems to go away. However, as soon as I build the project again, I have to re-do the same procedure.
On the other hand, creating a hello world binary that includes in its deps attributes the atlassian target works fine; therefore it would be worth figuring out why the codegen dependencies make rules_jvm_external do something different.
The maven/BUILD file for the codegen looks like this:
The error is being thrown because the first of its deps does not exist under that name.
Proposed Solution Indagate what is causing the discrepancy/add an alias.