[ELY-2932] removed obsolete javadoc config element. Documentation added#84
[ELY-2932] removed obsolete javadoc config element. Documentation added#84rsearls wants to merge 1 commit intowildfly-security:3.xfrom
Conversation
|
@rsearls This needs a dedicated ELYEE jira issue |
| </goals> | ||
| <configuration> | ||
| <destDir>full-javadoc</destDir> | ||
| <show>private</show> |
There was a problem hiding this comment.
@rsearls Just minor, if the destDir element is removed, is the resulting directory named the same, so "full-javadoc" ?
There was a problem hiding this comment.
I created https://issues.redhat.com/browse/ELY-2983 .
How should I handle associating this PR with the new jira.
"destDir" is not longer a supported property in maven-javadoc-plugin:3.11.2 and the documented property, "outputDirectory" is ignored by this plugin version.
The javaDoc for aggregate-jar is written to ./target, for aggregate it is
written to ./target/reports/apidocs .
There was a problem hiding this comment.
@rsearls To merge the commit into this repo, it should mention a jira issue from the project ELYEE here https://issues.redhat.com/projects/ELYEE/issues , it is a separate project from ELY.
Thanks for explanation!
There was a problem hiding this comment.
I have a branch with update in https://github.com/wildfly-security/wildfly-elytron-ee.git
I created https://issues.redhat.com/browse/ELYEE-100 Correct Javadoc Generation for all modules (branch 3.x)
I submitted to that project #86
Does this look OK?
Should I close this PR now?
2 participants
This jira https://issues.redhat.com/browse/ELYEE-100 supersedes the one below.
(this jira reference is obsolete https://issues.redhat.com/browse/ELY-2932)