8000 Remove therapi configuration · scijava/pom-scijava-base@4704d2c · GitHub
[go: up one dir, main page]

Skip to content

Commit 4704d2c

Browse files
committed
Remove therapi configuration
Nothing uses it anymore, as far as I know. The scijava-ops project switched to a custom annotation processor.
1 parent ef52b82 commit 4704d2c

File tree

1 file changed

+0
-52
lines changed

1 file changed

+0
-52
lines changed

pom.xml

Lines changed: 0 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -231,22 +231,6 @@
231231
<scijava.natives.classifier.javacpp>${scijava.platform.family.longest}-${scijava.platform.arch.javacpp}</scijava.natives.classifier.javacpp>
232232
<scijava.natives.classifier.jogamp>natives-${scijava.platform.family.longest}-${scijava.platform.arch.jogamp}</scijava.natives.classifier.jogamp>
233233

234-
<!--
235-
NB: The javadoc.runtimeAccessPackages property allows downstream
236-
projects to identify directories whose Javadoc should be made available
237-
at runtime. This javadoc can then be accessed through
238-
therapi-runtime-javadoc. By default, Javadoc is not available for any
239-
packages. Downstream projects can identify a comma-delineated set of
240-
packages to make those packages' Javadoc available. To retain some
241-
packages, override the javadoc.runtimeAccessPackages property in your
242-
POM with something like this:
243-
<javadoc.runtimeAccessPackages>com.example.foo,com.example.bar</javadoc.runtimeAccessPackages>
244-
To retain all packages, override the javadoc.runtimeAccessPackages
245-
property in your POM with:
246-
<javadoc.runtimeAccessPackages />
247-
-->
248-
<javadoc.runtimeAccessPackages>-</javadoc.runtimeAccessPackages>
249-
250234
<!-- Additional configuration -->
251235

252236
<!-- NB: Avoid platform encoding warning when copying resources. -->
@@ -324,8 +308,6 @@
324308
<kotlin.version>1.9.22</kotlin.version>
325309
<revapi-java.version>0.28.1</revapi-java.version>
326310
<scijava-coding-style.version>2.1.1</scijava-coding-style.version>
327-
<therapi.version>0.12.0</therapi.version>
328-
<com.github.therapi.therapi-runtime-javadoc-scribe.version>${therapi.version}</com.github.therapi.therapi-runtime-javadoc-scribe.version>
329311
<velocity.version>1.7</velocity.version>
330312

331313
<!-- Build extensions -->
@@ -357,40 +339,6 @@
357339
<plugin>
358340
<artifactId>maven-compiler-plugin</artifactId>
359341
<version>${maven-compiler-plugin.version}</version>
360-
<!--
361-
TEMP: Disable therapi until we solve why it fails on OpenJDK 8.
362-
The error is:
363-
364-
Compilation failure
365-
[ERROR] javac: invalid flag: -
366-
[ERROR] Usage: javac <options> <source files>
367-
[ERROR] use -help for a list of possible options
368-
369-
Or if you override javadoc.runtimeAccessPackages to anything else:
370-
371-
Compilation failure
372-
[ERROR] javac: invalid flag:
373-
[ERROR] Usage: javac <options> <source files>
374-
[ERROR] use -help for a list of possible options
375-
376-
Either way, it seems the -Ajavadoc.packages=... argument is not
377-
being passed to javac properly by the maven-compiler-plugin, even
378-
though the "mvn -X" looks correct and works standalone copy-pasted.
379-
380-
<configuration>
381-
<annotationProcessorPaths>
382-
<path>
383-
<groupId>com.github.therapi</groupId>
384-
<artifactId>therapi-runtime-javadoc-scribe</artifactId>
385-
<version>${com.github.therapi.therapi-runtime-javadoc-scribe.version}</version>
386-
</path>
387-
</annotationProcessorPaths>
388-
<fork>true</fork>
389-
<compilerArgs>
390-
<arg>-Ajavadoc.packages=${javadoc.runtimeAccessPackages}</arg>
391-
</compilerArgs>
392-
</configuration>
393-
-->
394342
</plugin>
395343

396344
<plugin>

0 commit comments

Comments
 (0)
0