-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make site deployment consistent #116
Comments
@khmarbaise on the second point (automatic site publish during release): this can't work for multi-module builds, because such build require site:stage during initial build then another build to do the scm-publish (from staging area) this is why there is the optimisation on mono-module builds, that don't require this staging extra step... I can't force you to prefer one single way to run site, then avoiding the mono-module optimisation, but I must avoid failure during release |
Currently we make a difference between mono module project and non mono module projects.
We should make it consistent and only use one way to go.
This means from my point of view:
maven-scm-publish-plugin
like this:Consequences
<scmpublish.content>target/staging/${project.artifactId}</scmpublish.content>
The text was updated successfully, but these errors were encountered: