Hi,
I'm using the Maven site plugin with a multi-module build. The generated
site is going to be deployed to GitHub, so I'm only using the Maven site
plugin to generate and stage content locally, not deploy.
I have a placeholder distributionManagement/site element in my POM so that
site:stage ca
yes, it is expected behaviour: see "inheritance assembly" step of model
builder [1]
in your case, your config cause artifactId to be added twice: one on
project.url and one on site.url before ${project.url} is interpolated
You should just not use ${project.url} in distributionManagement/site: t
Hi Hervé,
Thanks very much for your help, that was the problem. I knew this problem
existed for SCM urls, but I don't know why I assumed that project urls
would not be affected.
I'm excited for MNG-5951, because that will reduce the boilerplate
necessary to interact with GitHub and other git-bas
