You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2024/07/14 15:09:00 UTC

[jira] [Assigned] (MJAVADOC-783) Invalid path when using TagletArtifact and TagletPath

     [ https://issues.apache.org/jira/browse/MJAVADOC-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov reassigned MJAVADOC-783:
---------------------------------------

    Assignee: Michael Osipov

> Invalid path when using TagletArtifact and TagletPath
> -----------------------------------------------------
>
>                 Key: MJAVADOC-783
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-783
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 3.6.3
>            Reporter: Rob Gordon
>            Assignee: Michael Osipov
>            Priority: Major
>
> 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:
> {code:java}
>         if (tagletpath != null && !tagletpath.isEmpty()) {
>             if (path.length() > 0) {
>                  path.append(File.pathSeparator);
>            }
>             path.append(JavadocUtil.unifyPathSeparator(tagletpath));
>         }
> {code}
> 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. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)