[
https://issues.apache.org/jira/browse/BEAM-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839762#comment-16839762
]
Luke Cwik commented on BEAM-7302:
---------------------------------
The dependencies were originally rewritten because the groupId/artifactId were
incorrect when publishing the pom.xml. Eventually the reason as to why they
were rewritten was so we could add the exclusions on each dep to prevent things
like guava-jdk5 from being pulled in transitively. If the publish plugin can
now handle this, we could remove a bunch of the rewriting logic.
> Dependencies are broken in SNAPSHOT pom files
> ---------------------------------------------
>
> Key: BEAM-7302
> URL: https://issues.apache.org/jira/browse/BEAM-7302
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Affects Versions: 2.14.0
> Reporter: Ismaël Mejía
> Assignee: Michael Luckey
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The generated pom in the SNAPSHOTS repository points to dependencies that
> don't have the correct name, for example [the beam-sdks-java-core
> pom|https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-core/2.14.0-SNAPSHOT/beam-sdks-java-core-2.14.0-20190514.072148-6.pom]
> points to
> {code}
> <dependency>
> <groupId>beam.model</groupId>
> <artifactId>pipeline</artifactId>
> <version>2.14.0-SNAPSHOT</version>
> <scope>compile</scope>
> </dependency>
> {code}
> but such groupId and artifactId do not exist (and have not existed in the
> past).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
