Note that builds that break on Java 11 due to Javadoc errors with unnamed modules _should_ be fixed when the next version of the Maven Javadoc Plugin is released (3.1.0 IIRC)
Gary On Sat, Feb 9, 2019 at 11:56 AM Gilles Sadowski <gillese...@gmail.com> wrote: > Hi. > > Le sam. 9 févr. 2019 à 17:10, Benedikt Ritter <brit...@apache.org> a > écrit : > > > > Hi, > > > > several component have are broken builds on the master branch. Should be > > change our policy for pushing to master to a pull request based model, > > where each change has to pass the CI pipeline first? I think this would > be > > better as pushing stuff to master and then fixing it afterwards. > > One thing to take into account is that some CI jobs break for "unknown" > reasons (e.g. due to new requirements by Jenkins). Few people looking > into these issues leads to builds staying broken for extended period of > times; it would quite annoying that pushing is prevented even though > local builds continue to work as usual. > > Gilles > > > > > Benedikt > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
