[
https://issues.apache.org/jira/browse/MNG-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630999#comment-17630999
]
ASF GitHub Bot commented on MNG-7588:
-------------------------------------
kwin commented on PR #862:
URL: https://github.com/apache/maven/pull/862#issuecomment-1308586382
I would like to migrate all usage of Maven Core from the old `descriptor` to
the new `immutabledescriptor` package. But the question is again, do we
consider interfaces like
https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/plugin/BuildPluginManager.java
API, i.e. do we need to evolve it in a backwards-compatible way? If yes,
should we introduce new interfaces relying on the immutable descriptor or just
add new methods to the existing interfaces?
> 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)
