We had build the maven site earlier and therefore our maven-parent POM contains various templates and best practices for the site generation. As we stopped using maven site for years, this is all obsolete clutter.
Now it even turned out that some workarounds made us use variables like ${user.dir} that however, get resolved by flatten-maven-plugin so you get crazy OS specific paths in POMs like here:
https://repo1.maven.org/maven2/com/devonfw/java/modules/devon4j-basic/2022.12.001/devon4j-basic-2022.12.001.pom
This POM contains file://D:\projects\devonfw\workspaces\stable\devon4j/target/maven-site what is kind of nuts.
As a solution, we should simply strip out all maven site related stuff.
We had build the maven site earlier and therefore our
maven-parent
POM contains various templates and best practices for the site generation. As we stopped using maven site for years, this is all obsolete clutter. Now it even turned out that some workarounds made us use variables like${user.dir}
that however, get resolved byflatten-maven-plugin
so you get crazy OS specific paths in POMs like here: https://repo1.maven.org/maven2/com/devonfw/java/modules/devon4j-basic/2022.12.001/devon4j-basic-2022.12.001.pom This POM containsfile://D:\projects\devonfw\workspaces\stable\devon4j/target/maven-site
what is kind of nuts.As a solution, we should simply strip out all maven site related stuff.