[ https://issues.apache.org/jira/browse/MNG-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630084#comment-17630084 ]
ASF GitHub Bot commented on MNG-7588: ------------------------------------- gnodet commented on PR #862: URL: https://github.com/apache/maven/pull/862#issuecomment-1306379838 > Ok, so when generating descriptor beans in a dedicated package, where should this live? IMHO it doesn't make sense to expose under https://github.com/apache/maven/tree/master/api/maven-api-core. This should rather be a private package (only for consumption of Maven Core and maybe Maven Plugin Tools). I don't think it would be useful to add this to the documented v4 API of Maven. So I am rather thinking about putting the new/clean/immutable plugin descriptor classes into `org.apache.maven.plugin.descriptor.v11`. WDYT? Sounds good to me. > Plugin Descriptor: Java Beans and Reader should be generated automatically > -------------------------------------------------------------------------- > > Key: MNG-7588 > URL: https://issues.apache.org/jira/browse/MNG-7588 > Project: Maven > Issue Type: Improvement > Components: Plugin API > Reporter: Konrad Windszus > Assignee: Konrad Windszus > Priority: Major > Labels: plugin-descriptor-1.1 > > Currently the code in {{o.a.m.plugin.descriptor}} is generated manually. That > requires additional maintenance effort and has the risk that the underlying > model and the classes are out of sync. Both Java beans and readers should be > generated automatically from the underlying model. -- This message was sent by Atlassian Jira (v8.20.10#820010)