maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Heinz Marbaise <khmarba...@gmx.de>
Subject Re: Building Javadocs and site on CI
Date Sat, 29 Dec 2018 10:20:29 GMT
Hi Enrico,

On 29/12/18 09:53, Enrico Olivelli wrote:
> Karl,
> 
> 
> Il giorno sab 29 dic 2018 alle ore 09:41 Karl Heinz Marbaise
> <khmarbaise@gmx.de> ha scritto:
>>
>> Hi Enrico,
>>
>> On 29/12/18 09:14, Enrico Olivelli 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.
>>
>>
>> Can you report which one?
> 
> this is the fix, mostly about <br> tags
> https://github.com/apache/maven-assembly-plugin/commit/a97fbb304d1924426f3e3137ba42de0f3d9ec6a0
> 
> I had errors like:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.7.1:site (default-site)
> on project maven-assembly-plugin: Error parsing
> '/home/eolivelli/dev/maven-assembly-plugin/target/generated-site/xdoc/assembly.xml':
> line [1511] Error parsing the model: end tag name </p> must match
> start tag name <br> from line 1508 (position: TEXT seen ...om the
> central repository\n        are allowed.\n        \n      </p>...
> @1511:11)  -> [Help 1]
> 
> 
> 
>>
>>
>>> Isn't it possible to run  "javadoc:javadoc site" on CI ?
>>>
>>> This way we won't commit broken/unreleasable stuff
>>>
>>
>> Usually the sites will be generated via:
>>
>> mvn -Preporting site site:stage
> That's how I got the errors
> 
>>
>> if ready than
>> mvn scm-publish:publish-scm
>>
>> See also the deploySite.sh script...
>>
>> Furthermore you have to do the release via
>>
>> mvn release:prepare release:perform -Dgpg.keyname=...
>>
>> first and afterwards you can change into the target/checkout
>> directory and make the sites via the above commands...
> 
> good
> I am following this guide
> https://maven.apache.org/developers/release/maven-project-release-procedure.html
> which points to:
> https://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven
> and
> https://maven.apache.org/developers/website/deploy-component-reference-documentation.html
> 
> I guess the part "Publishing versioned component reference
> documentation" is to be done AFTER the VOTE as passed
> 
I'm a little bit late but it looks you did it the right way....



And yes the publishing is done after the VOTE is successful.

> So now master branch is stable, site is building correctly, PGP works
> as expected, I will prepare the release.
> 
> Let me try to summarize the guide and your answer:
> 
> mvn release:clean
> mvn release:prepare
> mvn release:perform

Usually you can clean up via:

git clean -fdx
and simple continue:

mvn release:prepare release:perform

in one go...

> cd target/checkout
> mvn -Preporting site site:stage
> mvn scm-publish:publish-scm
> 
> call for VOTE
> hopefully get 3 +1 from PMCs

That what you need at least...;-)...

> 
> finalize the release
> https://maven.apache.org/developers/release/maven-project-release-procedure.html
> 
> then update the website:
> https://maven.apache.org/developers/website/component-reference-documentation-helper.html?plugins
> 
> Is this correct ?

Published site looks ok so far...

Kind regards
Karl Heinz Marbaise
> 
> Thank you
> Enrico
> 
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message