Details
-
Type:
Task
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.2.0, CP-5.2.0
-
Component/s: Clients, Components, Container, Registry Overlay, Tools
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|
|
||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Priority | Major [ 3 ] | |
| Description |
During build, when generating Javadoc:
* if built with JDK 8 Oracle, all javadoc checks are activated by default, * if built with OpenJDK 8, javadoc checks are not activated. So the built result depends on the JDK used. To avoid this, we should define ourself to activate javadoc checks through the configuration of the maven-javadoc-plugin. In the same time, we could upgrade version of maven-javadoc-plugin: {code} <properties> <maven-javadoc-plugin.version>3.0.1</maven-javadoc-plugin.version> </properties> <plugin> ... <artifactId>maven-javadoc-plugin</artifactId> <version>${maven-javadoc-plugin.version}</version> <configuration> <doclint>all</doclint> </configuration> <executions> ... </executions> </plugin> {code} |
During build, when generating Javadoc:
* if built with JDK 8 Oracle, all javadoc checks are activated by default, * if built with OpenJDK 8, javadoc checks are not activated. So the built result depends on the JDK used. To avoid this, we should define ourself to activate javadoc checks through the configuration of the maven-javadoc-plugin. In the same time, we could upgrade version of maven-javadoc-plugin: {code:xml} <properties> <maven-javadoc-plugin.version>3.0.1</maven-javadoc-plugin.version> </properties> <plugin> ... <artifactId>maven-javadoc-plugin</artifactId> <version>${maven-javadoc-plugin.version}</version> <configuration> <doclint>all</doclint> </configuration> <executions> ... </executions> </plugin> {code} |
| Description |
During build, when generating Javadoc:
* if built with JDK 8 Oracle, all javadoc checks are activated by default, * if built with OpenJDK 8, javadoc checks are not activated. So the built result depends on the JDK used. To avoid this, we should define ourself to activate javadoc checks through the configuration of the maven-javadoc-plugin. In the same time, we could upgrade version of maven-javadoc-plugin: {code:xml} <properties> <maven-javadoc-plugin.version>3.0.1</maven-javadoc-plugin.version> </properties> <plugin> ... <artifactId>maven-javadoc-plugin</artifactId> <version>${maven-javadoc-plugin.version}</version> <configuration> <doclint>all</doclint> </configuration> <executions> ... </executions> </plugin> {code} |
During build, when generating Javadoc:
* if built with JDK 8 Oracle, all javadoc checks are activated by default, * if built with OpenJDK 8, javadoc checks are not activated. So the built result depends on the JDK used. To avoid this, we should define ourself to activate javadoc checks through the configuration of the maven-javadoc-plugin. In the same time, we could upgrade version of maven-javadoc-plugin: {code:xml} <properties> <maven-javadoc-plugin.version>3.0.1</maven-javadoc-plugin.version> </properties> <plugin> ... <artifactId>maven-javadoc-plugin</artifactId> <version>${maven-javadoc-plugin.version}</version> <configuration> <doclint>all</doclint> </configuration> <executions> ... </executions> </plugin> {code} |
| Fix Version/s | 5.3.0 [ 10908 ] | |
| Fix Version/s | CP-5.3.0 [ 10909 ] |
| Summary | Force activation of all checks duing javadoc generation | Force activation of all checks during javadoc generation |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Link |
This issue blocks |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Javadoc checks activated by svn#43166
maven-javadoc-plugin bumped to 3.2.0 by svn#43542 (
PETALSDISTRIB-419)PETALSDISTRIB-419)