Plugins on the old branch should have working javadoc for the most part. If anything else is missing it will flush out when/if we convert the site jobs over.

Still working on this for the branch. For expedience-sake, the plugins (which tend to reference older IdP versions) will be hard-wired for now to reference the published docs, which are fixed versions. This is somewhat like the original workaround we used in the old parent, except that it’s specific to each project and easier to realize needs to be adjusted.

It’s unlikely the old plugins will see a lot of subsequent releases, and even if thet do they likely won’t actually be moved to a later IdP version, so these workarounds are probably permanent until we sunset the branch.

Yeah, only the release profile activates the Javadoc plugin. Well, unless you activate explicitly on the command line of course.

As “expected?”, I guess the main compile/install goals do not build the individual or aggregated docs. It’s the release profile that turns that on. So, if we want to change to the aggregated jar, I think we just have to change the release profile’s config to use that goal instead of jar and test-jar. OTOH, I suspect perhaps that Eclipse might actually want those individual jars to be available to expose them as tool tips, particularly for released versions. Probably will need to play with that.

Commit 626939c to java-idp-plugin-totp