jira-importer commented on issue #762: URL: https://github.com/apache/maven-javadoc-plugin/issues/762#issuecomment-2957350425
**[Thorsten Schöning](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tschoening)** commented > And yes, when asking for a test to reproduce this issue and having no response for a long time is a good reason to close it as incomplete[...] The ticket creator waited almost two years for any reaction of anyone. > I would expect that for all file-related javadoc argument an equivalant plugin parameter should be available[...] Have a look at my use-case reported above: Axis 2 is using some custom doclet with some custom argument and that argument is forwarded using the options file created by the plugin. How should this use-case be handled? Should nobody use custom doclets with custom arguments and instead add options to the Maven plugin? Or do all users of pom.xml like that of Axis 2 fix the builds on their own, like I needed to do? Or is it the responsibility of the Maven-plugin to provide correct option files, which it currently doesn't for some cases? https://github.com/wso2/wso2-axis2-transports/blob/master/modules/testkit/src/main/java/org/apache/axis2/transport/testkit/doclet/ResourceInfoDoclet.java#L121 -- 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
