jira-importer opened a new issue, #1153:
URL: https://github.com/apache/maven-javadoc-plugin/issues/1153

   **[Alexander 
Kriegisch](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kriegaex)**
 opened 
**[MJAVADOC-775](https://issues.apache.org/jira/browse/MJAVADOC-775?redirect=false)**
 and commented
   
   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`.
   
   
   ---
   
   **Affects:** 3.6.0, 3.6.3
   
   **Issue Links:**
   - [MJAVADOC-783](https://issues.apache.org/jira/browse/MJAVADOC-783) Invalid 
path when using TagletArtifact and TagletPath
    (_**"duplicates"**_)
   
   **Remote Links:**
   - [GitHub Pull Request #255
   ](https://github.com/apache/maven-javadoc-plugin/pull/255)
   
   0 votes, 5 watchers
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to