This one is clearly the one I was fearing last time you reported an issue parent pom still has old svnpubsub url, causing unwanted relative path Should either release parent pom or use m-site-p topParentUrl param to force relative path calculations (like multi module builds)
Regards Hervé (not completely offline at the moment, but not sure how long it will last...) ----- Mail d'origine ----- De: Karl Heinz Marbaise <khmarba...@gmx.de> À: Maven Developers List <dev@maven.apache.org> Envoyé: Fri, 17 Apr 2015 16:37:45 +0200 (CEST) Objet: Problems during the Release with the Site site:stage Hi, so after a time i had done an other releases and found out the following: I do the release like: mvn release:prepare ...release:perform cd target/checkout mvn -Preporting site site:stage now mvn scm-publish:publish-scm but unfortunately the published site doesn't contain the correct content...But why does this happened... So... for example i'm releasing the maven-javadoc-plugin ok..go into the target/checkout folder to stage the site... mvn site:stage will copy content into target/checkout/../components/plugins-archives/maven-javadoc-plugin-LATEST/... which isn't transfered to the online site via mvn scm-publish... So either i'm doing something really weird / stupid things which i don't see at the moment or the exists a problem... Kind regard Karl Heinz Marbaise --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
