jira-importer commented on issue #691: URL: https://github.com/apache/maven-javadoc-plugin/issues/691#issuecomment-2957344640
**[David Liszewski](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cruelfate)** commented I do wonder if history will show this to be an ill-advised change. Regard http://stackoverflow.com/questions/25983852/maven-javadoc-plugin-breaks-mvn-releaseperform/25986409#25986409 http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim http://jira.codehaus.org/browse/MJAVADOC-406 I fail to understand how it was _your_ responsibility to provide a work-around for an [*unresolved* defect](https://bugzilla.redhat.com/show_bug.cgi?id=1113877) in `java-1.8.0-openjdk`. Yes, I know we should be pinning plug-in versions. For certain, this is a wake-up call for the community to change their behavior, but it was a rather rude awakening. We'll be editing a few hundred files so we can make update releases for our clients. Multiply that by the number of users of this plugin. The grief reported on StackOverflow is but a tip of the iceberg. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
