I've already introduces the concept of "plans"[1][2], which also include
'site' for documentation and 'release' to verify if the project is
releasable (should probably change that name to prevent confusion).
The jobs are getting more stable, so we might give it a try soon. Just
need to be aware that the 'site' plan doesn't seem to work for multimodule
projects yet. Better fix that first.
thanks,
Robert
[1]
https://gitbox.apache.org/repos/asf?p=maven-jenkins-lib.git;a=blob;f=vars/asfMavenTlpPlgnBuild.groovy;h=6502fe80819c873757e339a0f1b3186fd14303b9;hb=HEAD#l63
[2]
https://gitbox.apache.org/repos/asf?p=maven-jenkins-lib.git;a=blob;f=vars/asfMavenTlpPlgnBuild.groovy;h=6502fe80819c873757e339a0f1b3186fd14303b9;hb=HEAD#l132
On Sat, 29 Dec 2018 09:14:27 +0100, Enrico Olivelli <[email protected]>
wrote:
Hi guys,
I am trying to release Maven Assembly Plugin and I see that there are
a few showstoppers due to javadocs and site generation.
Isn't it possible to run "javadoc:javadoc site" on CI ?
This way we won't commit broken/unreleasable stuff
Enrico
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
