Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.6.3
-
None
-
None
-
None
Description
I’m trying to use the Javadoc plugin with both a tagletartifact and a tagletpath but I get an InvliadPathException from the Javadoc goal.
I can see from the generated options file that there is no separator between the end of the artifact path and the taglet path.
I think the problem is that getTagletPath method of AbstractJavadocMojo should check for an existing path before adding the tagletpath. Something like:
if (tagletpath != null && !tagletpath.isEmpty()) { if (path.length() > 0) { path.append(File.pathSeparator); } path.append(JavadocUtil.unifyPathSeparator(tagletpath)); }
I looked at creating a pull request but I can’t work out how to create a suitable test. I found a taglet-test-plugin-config.xml, but not where it’s used.
Could someone familiar with this codebase possibly take a look at this problem please?
My configuration can be seen here: https://github.com/robjg/oj-parent/blob/d3e2328ca285516f1a4f6ee2bce94b44ba89b748/pom.xml#L304
I attempted to report this problem via 'users@maven.apache.org' however my mail did not make it.
Attachments
Issue Links
- is duplicated by
-
MJAVADOC-775 Option 'taglets/taglet/tagletpath' ignored when pointing to a JAR
-
- Closed
-
- links to