Re: Beam parent SNAPSHOTs are not being built

I can try triggering a one-off maven snapshot release. On Thu, Apr 26, 2018 at 1:59 PM Eric Beach wrote: > Is it possible to trigger a manual task to update the snapshot artifacts > here in the interim until a decision has been made? It is blocking dev > toward a public release. > > On Thu, Apr

Re: Beam parent SNAPSHOTs are not being built

Is it possible to trigger a manual task to update the snapshot artifacts here in the interim until a decision has been made? It is blocking dev toward a public release. On Thu, Apr 26, 2018 at 2:51 AM Romain Manni-Bucau wrote: > > > 2018-04-26 7:54 GMT+02:00 Reuven Lax : > >> This seems more tha

Re: Beam parent SNAPSHOTs are not being built

2018-04-26 7:54 GMT+02:00 Reuven Lax : > This seems more than just Gradle, as they are using internal details in > the parent pom (all the Google Cloud dependency version). Saying that > nothing should break means that we can never rename or refactor anything in > our poms because some user might

Re: Beam parent SNAPSHOTs are not being built

This seems more than just Gradle, as they are using internal details in the parent pom (all the Google Cloud dependency version). Saying that nothing should break means that we can never rename or refactor anything in our poms because some user might be depending on it; that would be true on Maven

Re: Beam parent SNAPSHOTs are not being built

Hmm, gradle move not supposed to break any user and there are other parents usages, as mentionned previously, so not sure beam can really bypass it. Maven discussed consumer vs build pom since years for that reason ;). Le 26 avr. 2018 01:59, "Eric Beach" a écrit : > Thanks Scott and Ben. > > Thi

Re: Beam parent SNAPSHOTs are not being built

Thanks Scott and Ben. This makes sense, and of course the same error happens when I tried beam-parent instead of beam-examples-parent. There is a big benefit for supporting explicit dependence on parent (either beam-examples-parent or beam-parent). In the project I'm involved in, I have Dataflow

Re: Beam parent SNAPSHOTs are not being built

Interesting. So two things: 1) As you correctly deduced, we switched to producing snapshots from the Gradle build, which doesn't include parent pom's. As a result, the parent pom snapshot you're referencing is stale. We should probably remove it from the repository to prevent accidental usage unti

Re: Beam parent SNAPSHOTs are not being built

It looks like the problem is that your project uses beam-examples-parent as its parent. This was the suggested way of creating a Maven project because we published a POM and this provided an easy way to make sure that derived projects inherited the same options and versions as Beam used. With the

Re: Beam parent SNAPSHOTs are not being built

If I run $ mvn clean compile exec:java ... on my project, I get the following error stack trace: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java

Re: Beam parent SNAPSHOTs are not being built

Ccing Eric for providing more context. Thanks, Cham On Wed, Apr 25, 2018 at 3:38 PM Scott Wegner wrote: > 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 me

Re: Beam parent SNAPSHOTs are not being built

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 J

Re: Beam parent SNAPSHOTs are not being built

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 wrote: >

Re: Beam parent SNAPSHOTs are not being built

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 wrote: > Thanks. Should this be a 2.5.0 blocker

Re: Beam parent SNAPSHOTs are not being built

Incidentally can we just eliminate parent modules? They don't do anything, do they? On Wed, Apr 25, 2018 at 2:07 PM Chamikara Jayalath wrote: > Thanks. Should this be a 2.5.0 blocker ? > > On Wed, Apr 25, 2018 at 2:05 PM Alan Myrvold wrote: > >> I think this corresponds with the move from maven

Re: Beam parent SNAPSHOTs are not being built

Thanks. Should this be a 2.5.0 blocker ? On Wed, Apr 25, 2018 at 2:05 PM Alan Myrvold 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

Re: Beam parent SNAPSHOTs are not being built

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 wrote: > Seems like we are not building some of the SNAPSHOT artifacts since > 4/9/2018. > For example

Beam parent SNAPSHOTs are not being built

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.