Hi, to unblock the release I'm changing the version manually now, yes. Would be good to fix though.
Cheers, Aljoscha On Mon, 24 Oct 2016 at 20:30 Dan Halperin <dhalp...@google.com.invalid> wrote: > Hmm, this is new in 0.3.0, looks caused by > > https://github.com/apache/incubator-beam/commit/1f30255edcdd9c1e445b69248191c8552724f086#diff-4795b1d2aaaa7449c01332aad192348eL111 > < > https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-beam%2Fcommit%2F1f30255edcdd9c1e445b69248191c8552724f086%23diff-4795b1d2aaaa7449c01332aad192348eL111&sa=D&sntz=1&usg=AFQjCNGOYTW7DSiNZuGnOKWuHhggzsnztQ > > > > Thinking if we can revert this part of the commit. Pei, Luke -- remember > what's up? > > On Mon, Oct 24, 2016 at 11:17 AM, Dan Halperin <dhalp...@google.com> > wrote: > > > Would it unblock the release to manually configure the version in the > > 0.3.0-release branch? > > > > On Mon, Oct 24, 2016 at 11:09 AM, Dan Halperin <dhalp...@google.com> > > wrote: > > > >> Correct issue link: https://issues.apache.org/jira/browse/BEAM-806 > >> > >> No answers, but looking around. > >> > >> On Mon, Oct 24, 2016 at 10:10 AM, Aljoscha Krettek <aljos...@apache.org > > > >> wrote: > >> > >>> Hi, > >>> are there any Maven mavens who happen to know how > >>> https://issues.apache.org/jira/browse/BEAM-108 can be fixed? By the > way, > >>> the release plugin does also not update the version of the archetypes > >>> when > >>> setting the next SNAPSHOT version. > >>> > >>> IMHO, it's a bit of a release blocker so I'm hoping we can get this > >>> sorted > >>> quickly. I did some preliminary research but couldn't find a solution > but > >>> if no-one knows how to fix it it seems I have to dig deeper myself. > >>> > >>> Cheers, > >>> Aljoscha > >>> > >> > >> > > >
