Ok So I "fixed" the problem even if I think it wasn't really a "problem".
The issue was, if you run "mvn site" on the root ... while I added the root pom to sort of glue together all the different parts, it should actually not be required as the project consists of multiple sub-projects within one repo. The issue now was that therefore the intermediate pom-artifacts didn't have parent poms set. Therefore the defaults of maven were used and these seem to have issues. I fixed the problem by correctly having all artifacts have parent pom chains that end at the apache parent pom. While I was at it I updated the parent poms of the live artifacts (not the released presentations) to the freshly released version 22. Also did I add a small "getting started" page in the user-space of the website to explain how to use the new tooling. Chris PS: Just noticed I need to update the documentation on how to add the apache snapshot repo to maven as long as we haven't released the tooling. Am 24.01.20, 10:08 schrieb "Sönke Liebau" <[email protected]>: Thanks Chris! On Fri, 24 Jan 2020 at 10:02, Christofer Dutz <[email protected]> wrote: > Just noticed ... > > the problem is not when building the project (mvn clean package) but when > building the site ... will investigate. > > Chris > > Am 24.01.20, 09:40 schrieb "Christofer Dutz" <[email protected]>: > > Argh ... just read this. > > I just built everything with an empty repo and it worked without any > problems. > > Chris > > > > Am 24.01.20, 03:42 schrieb "Justin Mclean" <[email protected]>: > > Hi, > > Never mind I managed to sort it out. > > Thanks, > Just > > > > > -- Sönke Liebau Partner Tel. +49 179 7940878 OpenCore GmbH & Co. KG - Thomas-Mann-Straße 8 - 22880 Wedel - Germany
