[
https://issues.apache.org/jira/browse/BEAM-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839656#comment-16839656
]
Kenneth Knowles commented on BEAM-7302:
---------------------------------------
But this makes me wonder - if we set things up correctly with publishing
plugin, why would be be manually building the pom.xml?
> 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
>
> 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)
