[
https://issues.apache.org/jira/browse/MJAVADOC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795591#comment-17795591
]
Alexander Kriegisch edited comment on MJAVADOC-775 at 12/13/23 1:49 AM:
------------------------------------------------------------------------
[~elharo], are you sure it is is godd idea to close this one? My
{{ClassNotFoundException}} is not the same as the {{InvalidPathException}} in
the other issue. The descriptions also sound different. Just because there
happen to be two issues about tagle paths, it does not automatically mean that
they are identical.
I also do not understand what you are missing here. There is a link to a
real-world reproducer with exact instructions which commit to check out. A link
to previous conversation on a mailing list about this, where you can also find
an error description, also exists. Usually, developers ask for reproducers and
links to further details. Sometimes, when providing same, I feel like they have
not been read.
was (Author: kriegaex):
[~elharo], are you sure it is is godd idea to close this one? My
{{ClassNotFoundException}} is not the same as the {{InvliadPathException}} in
the other issue. The descriptions also sound different. Just because there
happen to be two issues about tagle paths, it does not automatically mean that
they are identical.
I also do not understand what you are missing here. There is a link to a
real-world reproducer with exact instructions which commit to check out. A link
to previous conversation on a mailing list about this, where you can also find
an error description, also exists. Usually, developers ask for reproducers and
links to further details. Sometimes, when providing same, I feel like they have
not been read.
> Option 'tagletpath' not working, completely ignored
> ---------------------------------------------------
>
> Key: MJAVADOC-775
> URL: https://issues.apache.org/jira/browse/MJAVADOC-775
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.6.0
> Reporter: Alexander Kriegisch
> Priority: Major
>
> The [{{tagletpath}}
> property|https://maven.apache.org/plugins/maven-javadoc-plugin/apidocs/org/apache/maven/plugins/javadoc/options/Taglet.html#getTagletpath()]
> used in a [{{taglets}}/{{taglet}}
> element|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#taglets]
> seems to be completely ignored, despite being documented. It looks as if
> this never worked before. It is also utterly untested. There is an old bug
> MJAVADOC-231, but whatever that was meant to fix, it seems to be unrelated to
> this one. If I have a local JAR unavailable on Maven Central sitting in a
> libraries folder, I cannot use it in any other way than to contrive to put a
> copy into my local Maven repository and use {{tagletArtifact}} instead of
> {{taglets}}/{{taglet}}/{{tagletpath}}.
> I noticed this, when trying to help someone asking a question on the [Maven
> users mailing
> list|https://lists.apache.org/thread/zv25z3hx9gbmbt6wwhby6cy0t5lr542l]. In
> his [sample repository|https://github.com/jkesselm/xalan-java-mvn], an effort
> to convert the Xalan Ant Build to Maven, the commit to check out is is
> [6daf2890|https://github.com/jkesselm/xalan-java-mvn/tree/6daf2890bc03b13cd741b963d33897d61dcf4e5f].
> Just run {{mvn -DskipTests=true site}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
