[SGF-626] Javadoc is not part of the distribution build Created: 09/May/17  Updated: 14/Jun/17  Resolved: 09/May/17

Status: Closed
Project: Spring Data GemFire
Component/s: None
Affects Version/s: 2.0 M3 (Kay)
Fix Version/s: 2.0 M4 (Kay)

Type: Bug Priority: Critical
Reporter: Mark Paluch Assignee: John Blum
Resolution: Fixed Votes: 0
Labels: datagemfire, javadoc, pivotalgemfire, spring
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Last updater: Mark Paluch


Javadoc is no longer distributed as part of the distribution build. Javadocs are expected in $project.baseDir/target/static-resources/api. Reference docs are built and distributed correctly.

Comment by John Blum [ 09/May/17 ]

Mark Paluch - what needs to be done here, exactly?

I am compared SDG's Maven POM with other SD modules (Commons, MongoDB, Redis) and I not seeing what needs to be changed in SDG to be on par with the other modules.


Comment by John Blum [ 09/May/17 ]

Mark Paluch - See comment above...

Comment by Mark Paluch [ 09/May/17 ]

Looks like the assembly plugin is executed before the Javadoc plugin is executed. Moving maven-assembly-plugin to the lower part, right before wagon-maven-plugin should help.

Comment by John Blum [ 09/May/17 ]

Ah crap... totally, my bad! I must have inadvertently moved things around when I was making changes to the POM file for asciidoc HTML generation during regular SDG build runs (without having to explicitly enable the Spring Data Build (parent) distribution Maven Profile).

Thanks Mark Paluch.

Generated at Sat Jul 11 05:56:55 UTC 2020 using Jira 8.5.4#805004-sha1:0444eab799707f9ad7b248d69f858774aadfd250.