jira-importer commented on issue #762:
URL: 
https://github.com/apache/maven-javadoc-plugin/issues/762#issuecomment-2957350482

   **[Thorsten 
Schöning](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tschoening)**
 commented
   
   In my opinion, the easiest solution is applying the regular expression and 
replacement I proposed. That fixes this issue, doesn't seem to break too much 
and more complex things can be implemented as really needed. [Ilya 
Basin](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=basinilya), 
what's your opinion about this? You actually created the bug, what would fit 
your needs best?
   
   Any more complex things, especially changing the schema and whatever stuff, 
wouldn't be used easily anyway, because the containing pom.xml would need to be 
migrated. In my case this issue is about a pom.xml from some 3rd party project 
that worked on Linux and wasn't ever tested on Windows by the developers, so 
failed for me. I'm not even sure if upstream accepted my patch with my 
mentioned workaround yet, so they won't likely rewrite their pom.xml to use 
newer stuff.
   
   The only good solution is one that works without changing the pom.xml, by 
relying only on people which are affected by the problem to simply update their 
own Maven. That is something I have control of. If I need to rewrite the 
pom.xml anyway, I could simply stick with my documented workaround. If you 
think otherwise, [Robert 
Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte) 
is correct, simply don't do anything because it won't help much.
   
   > Are you willing to raise an issue with Oracle to at least clarify the 
documentation.
   
   I'm not sure who to write at currently, so started a question on SO first:
   
   
https://stackoverflow.com/questions/53949999/who-is-responsible-for-docs-and-implementation-of-the-javadoc-tool
   


-- 
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

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

Reply via email to