Based on my testing locally and in a clean environment.. When I have tamaya's main repo checked out and built locally, with the parent set to tamaya, the codehaus repos are not in my reactor.
When I don't have tamaya built locally, then the codehaus repos are in my reactor. John On Sun, Nov 6, 2016 at 2:21 PM Oliver B. Fischer <[email protected]> wrote: > You can check the known/active repositorys by running mvn > dependency:list-repositories > > > Am 06.11.16 um 15:26 schrieb John D. Ament: > > I suspect the underlying issue is that we're pointing to a non-relative > > snapshot release. Snapshots are not in maven central, so maven is using > > its internal logic to known repositories. This I suspect is activating > the > > legacy codehaus repos. > > > > John > > > > On Sun, Nov 6, 2016 at 4:43 AM P. Ottlinger <[email protected]> > wrote: > > > >> Am 05.11.2016 um 01:10 schrieb Oliver B. Fischer: > >> Maybe this problem is related to the problem with the site build - > >> it's also unable to resolve codehaus.org > >> > >> Phil > >> > > -- > N Oliver B. Fischer > A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany > P +49 30 44793251 <+49%2030%2044793251> > M +49 178 7903538 <+49%20178%207903538> > E [email protected] > S oliver.b.fischer > J [email protected] > X http://xing.to/obf > >
