[
https://issues.apache.org/jira/browse/MNG-8485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911026#comment-17911026
]
Guillaume Nodet commented on MNG-8485:
--------------------------------------
{quote}There's of course no technical reason. This is about the developer
experience.{quote}
It seems to me that this is a communication / documentation problem.
And if we look at
https://github.com/apache/maven-site/blob/99ea2cca3ee1fbce6b4b16f7ee53966473a441a3/content/markdown/whatsnewinmaven4.md
(which I haven't written), the new API is not even mentioned.
Of course, given we deprecated a lot of Maven 3 APIs, if developers start
writing plugins and use Maven 4 dependencies, they will probably see all those
warnings that redirect them to the new API. We'll have to communicate clearly
the state of the API, the fact that we're still in preview and need feedback.
{quote}Preview APIs are a thing, but I also don't think it's OK to release most
major APIs for core functionality as preview.{quote}
Not sure to follow. I would think the exact opposite. Since it's such a big
thing, we definitely want to make sure it's mature and stable before making it
official. We could delay Maven 4 another few years, but it still contains new
features that are useful to users, so I'd rather have a way to delivery those
and have a more iterative release schedule, rather than delaying for years.
{quote}I'm not sure what you mean by "No plugins have been officially released
in GA". We don't seem to use the term GA in the Maven project, but dozens of
plugins have been released and stable post-1.0 for years. I'd call that
GA.{quote}
Sorry, I was unclear. I meant that we have not released any stable plugin
using the new Maven API. We did release a few in beta only.
> Finish experiments and commit
> -----------------------------
>
> Key: MNG-8485
> URL: https://issues.apache.org/jira/browse/MNG-8485
> Project: Maven
> Issue Type: Task
> Affects Versions: 4.0.0-rc-2
> Reporter: Elliotte Rusty Harold
> Priority: Blocker
>
> Roughly 200 classes and interfaces in Maven core are annotated
> `@Experimental` . There might be a reason to ship a few things in 4.0 that
> might still change but 200 is far too many. Commit to these APIs (i.e. remove
> the annotation) or fix and/or remove those types.
> Ar least some of them such as org.apache.maven.api.services.BaseRequest are
> already package protected, in which case we don't need the annotation at all.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
