Oh. Duh.
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.6.0</version>
<scope>system</scope>
<systemPath>${toolsjar}</systemPath>
</dependency>
On 10/3/2023 10:04 PM, Alexander Kriegisch wrote:
Hi Joseph.
I think you uncovered a bug in Maven Javadoc Plugin. I just created
https://issues.apache.org/jira/browse/MJAVADOC-775 on your behalf.
As a workaround for the non-functioning 'tagletpath' option, I recommend
to separately publish the taglet library as a Maven artifact, which then
you can refer to using the 'tagletArtifact' option. The hypothetical
workaround to just use a system-scoped dependency and refer to that in
'tagletArtifact', is not working either. So, until this will have been
fixed, your options are very limited.
Because I was looking at the two simple taglet classes in your JAR
anyway from my IDE when analysing your problem, in the attached ZIP
archive is the decompiled source code for both classes, just in case you
do not have the sources anymore and want to recreate the JAR as a
separate artifact. I hope that the mailing list does not strip off
attachments.
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
