[
https://issues.apache.org/jira/browse/MPLUGIN-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849026#comment-17849026
]
ASF GitHub Bot commented on MPLUGIN-525:
----------------------------------------
gnodet commented on PR #285:
URL:
https://github.com/apache/maven-plugin-tools/pull/285#issuecomment-2127541125
> > > Is this Maven 4 only?
> >
> >
> > Yes, I've created a [3.x
branch](https://github.com/apache/maven-plugin-tools/tree/3.x) to support Maven
3 plugins and master will support Maven 4 plugins. The goal is to split the
plugins to ease maintenance, as the code will ultimately be quite different.
See https://issues.apache.org/jira/browse/MPLUGIN-523. We should also drop the
Maven 4.x support from the 3.x branch.
>
> I see. There is no way to have this in one branch with common modules and
module per Maven version?
Sure, I suppose it's technically feasible, but instead of streamlining and
making the code simpler, it will have the exact opposite effect.
The javadoc generator is now irrelevant, and the generator one, while I kept
a single one for the alpha versions, is becoming more problematic, as the API
seems to diverge a bit with the Maven 3 one. We currently generate a
plugin.xml but this is all tacky as it assumes there's no difference between
the 3.x and 4.x ones. We do have a writer which is generated in Maven 4 which
we could use to write the plugin.xml (do we really need it btw ?). I was hoping
to clean things and avoids lots of hacks to make the code more robust.
> Remove ant and beanshell support
> --------------------------------
>
> Key: MPLUGIN-525
> URL: https://issues.apache.org/jira/browse/MPLUGIN-525
> Project: Maven Plugin Tools
> Issue Type: Task
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 4.0.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
