[RELENG-42] Produce JavaDoc site for entire release Created: 28/Feb/17  Updated: 10/Aug/20

Status: Open
Project: releng
Component/s: Autorelease
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Michael Vorburger Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Blocks
blocks DOCS-33 javadoc.opendaylight.org Open
blocks RELENG-3 Javadocs are not being generated for ... Open
is blocked by ODLPARENT-70 New odlparent Maven Profile / Parent ... Resolved
External issue ID: 7873

 Description   

based on discussions rovarga, zxiiro and I just had on IRC:

Once ODLPARENT-70 is implemented, then (quote rovarga) "integration/distribution can produce the javadoc site for all that goes into the release"

 Comments   
Comment by Vratko Polak [ 01/Mar/17 ]

Are you sure this is for Integration/Distribution? Sounds more like a task for Releng/Autorelease instead. There might be Java-based components to be run outside Karaf, for example netconf-testtool. And even for code inside Karaf, Int/Dist only refers to Karaf features, it lacks mechanisms to discover javadocs.

On the other hand, Releng/Autorelease builds everything related to a release, including Maven Sites (not sure about ReadTheDocs) so it is in better position to determine which javadocs should be included.

Comment by Michael Vorburger [ 01/Mar/17 ]

> Are you sure this is for Integration/Distribution?

no, not sure at all! Filed this here based on a quick high-level chat with Robert (above) on IRC last night, without further thought, I admit.

> On the other hand, Releng/Autorelease

OK, I've moved this bug from Integration/Distribution to Releng/Autorelease then. Anyway this will only be ready to be looked at further after ODLPARENT-70 starts moving.

Generated at Wed Feb 07 20:37:21 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.