I removed it from the parent POM. Which module/pom has the alteration? It's strange, the "effective" POM based on Apache Parent 18 also points to a central repo that now includes AssertJ, so judging from that it should not have been necessary to change any module.
On Sun, Jan 29, 2017 at 9:56 PM, Werner Keil <[email protected]> wrote: > Ok, that's not the parent module, is it? > https://issues.apache.org/jira/browse/TAMAYA-216 > states > > - Needed to add another maven repo to fetch assertj. > > > > > > On Sun, Jan 29, 2017 at 9:50 PM, P. Ottlinger <[email protected]> > wrote: > >> Am 29.01.2017 um 21:48 schrieb Werner Keil: >> > Unfortunately the Apache parent pom (we use v 18) does not point to >> > MavenCentral and see at least 1 or more Hangout minutes, the "Central >> > repository" points to >> > <name>Central Repository</name> >> > <url>https://repo.maven.apache.org/maven2</url> >> > >> > It does look like AssertJ is in there now, so do we know from JIRA what >> was >> > the problem with AssertJ? >> > https://repo.maven.apache.org/maven2/org/assertj/ >> >> That's exactly the reason why I've added maven2central to the project >> that uses AssertJ at the moment. >> >> Phil >> > >
