Do you have any more context on how they were using the parent pom? In the Gradle build, instead of using a parent pom hierarchy we are embedding the complete set of dependencies and metadata in each generated pom. They should be functionally equivalent.
On Wed, Apr 25, 2018 at 3:09 PM Chamikara Jayalath <chamik...@google.com> wrote: > At least one user was depending on 'beam-parent' and ran into issues due > to dependency update https://github.com/apache/beam/pull/5046 not being > reflected there. I'm not sure if this is a usage pattern that we should > discourage. > > Thanks, > Cham > > > On Wed, Apr 25, 2018 at 2:36 PM Alan Myrvold <amyrv...@google.com> wrote: > >> The gradle build is currently only generating pom files when there is a >> jar file. >> What are these parent poms used for? Do all the parent poms need to be >> generated or just the top level beam-parent? >> >> On Wed, Apr 25, 2018 at 2:07 PM Chamikara Jayalath <chamik...@google.com> >> wrote: >> >>> Thanks. Should this be a 2.5.0 blocker ? >>> >>> On Wed, Apr 25, 2018 at 2:05 PM Alan Myrvold <amyrv...@google.com> >>> wrote: >>> >>>> I think this corresponds with the move from maven to gradle snapshot >>>> releases. >>>> Issue logged as https://issues.apache.org/jira/browse/BEAM-4170 >>>> >>>> On Wed, Apr 25, 2018 at 1:57 PM Chamikara Jayalath < >>>> chamik...@google.com> wrote: >>>> >>>>> Seems like we are not building some of the SNAPSHOT artifacts since >>>>> 4/9/2018. >>>>> For example: >>>>> >>>>> >>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-parent/2.5.0-SNAPSHOT/ >>>>> >>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-examples-parent/2.5.0-SNAPSHOT/ >>>>> >>>>> Users who depend on these artifacts are getting outdated dependencies. >>>>> >>>>> Any idea why ? >>>>> >>>>> Thanks, >>>>> Cham >>>>> >>>> -- Got feedback? http://go/swegner-feedback
