|
115 | 115 | <junit.version>4.12</junit.version>
|
116 | 116 | <junit.jupiter.version>5.5.0</junit.jupiter.version>
|
117 | 117 | <powermock.version>2.0.2</powermock.version>
|
118 |
| - <protobuf.version>3.8.0</protobuf.version> |
| 118 | + <protobuf.version>3.9.0</protobuf.version> |
119 | 119 | <mockito-core.version>3.0.0</mockito-core.version>
|
120 | 120 | <guava.version>28.0-jre</guava.version>
|
121 | 121 | <vertx.version>3.7.1</vertx.version>
|
|
421 | 421 | <configuration>
|
422 | 422 | <source>${java.compiler.source}</source>
|
423 | 423 | <doclint>none</doclint>
|
424 |
| - <!-- Allow fetching links below --> |
425 |
| - <isOffline>false</isOffline> |
426 | 424 | <detectOfflineLinks>false</detectOfflineLinks>
|
427 |
| - <links> |
428 |
| - <!-- Published Exonum API docs. Only the modules that are dependencies of |
429 |
| - other modules are listed here. |
430 |
| -
|
431 |
| - To generate release Javadocs, a two-step process is required: |
432 |
| - 0. Bump version. |
433 |
| - 1. Generate Javadocs for the given version. They won't have cross-references, |
434 |
| - because no Javadocs have been published on the website. |
435 |
| - 2. Upload them to the website. |
436 |
| - 3. Re-generate Javadocs. This time the Javadocs will be available |
437 |
| - on the website, and cross-references will be added. |
438 |
| - 4. Upload the new ones. |
439 |
| -
|
440 |
| - Our web-site seems to be the only one compatible with javadoc tool — |
441 |
| - the Javadocs published on javadoc.io, github.io (guava and vertx) |
442 |
| - do not work. |
443 |
| - --> |
444 |
| - <link>https://exonum.com/doc/api/java-binding-common/${project.version}</link> |
445 |
| - <link>https://exonum.com/doc/api/java-binding-core/${project.version}</link> |
446 |
| - </links> |
447 | 425 | <additionalJOption>${maven.javadoc.joption}</additionalJOption>
|
448 | 426 | </configuration>
|
449 | 427 | <executions>
|
|
0 commit comments