[
https://issues.apache.org/jira/browse/MJAVADOC-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795132#comment-17795132
]
Alexander Kriegisch edited comment on MJAVADOC-783 at 12/11/23 1:02 AM:
------------------------------------------------------------------------
{quote}I attempted to report this problem via 'us...@maven.apache.org' however
my mail did not make it. {quote}
Even after a quarter of the 21st century has passed, Apache mailing lists
stubbornly insist on only accepting plain text messages. I am sure, that saves
the Internet bandwidth-wise and the planet as a whole, and everyone still reads
e-mails on text consoles. I actually also like to write plain text messages,
even in business. But sometimes, it makes sense to have some formatting for
inline code blocks and them not being butchered by word wrap, or to insert some
explanatory inline pics, making the message so much easier and quicker to read
than attaching same pics and code blocks as extra files which the reader then
has to open one by one, trying to fully understand the message.
Sorry to all sensitive souls for the snarky comment, but I could not resist and
am gladly taking all your blame.
was (Author: kriegaex):
{quote}I attempted to report this problem via 'us...@maven.apache.org' however
my mail did not make it. {quote}
Even after a quarter of the 21st century has passed, Apache mailing lists
stubbornly insist on only accepting plain text messages. I am sure that saves
the Internet bandwidth-wise, and everyone still reads e-mails on text consoles.
I actually also like to write plain text messages, even in business. But
sometimes, you want to have some formatting for inline code blocks and them not
being butchered by word wrap or insert some explanatory inline pics, making the
message so much easier and quicker to read than attaching same pics and code
blocks as extra files which the reader then has to open one by one, trying to
fully understand the message.
Sorry to all sensitive souls for the snarky comment, but I could not resist and
am gladly taking all your blame.
> 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
> 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 'us...@maven.apache.org' however my
> mail did not make it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
