[
https://issues.apache.org/jira/browse/MNG-8485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911117#comment-17911117
]
Guillaume Nodet commented on MNG-8485:
--------------------------------------
{quote}There are two APIs: the deprecated one and the one that doesn't work
yet. We shouldn't be deprecating things until the replacement is ready.{quote}
Yes, that's right. I'm not sure this is a big problem as it's not really as if
you could use one or the other and mix/match. Those are two separate worlds:
Maven 3 plugins and Maven 4 plugins. Plugin developers will need to choose a
target and I think developers that want to write a Maven 3 plugins should use
the Maven 3 artifacts (where the Maven 3 API is not deprecated).
It's not as if we were deprecating one class or method in favour of another:
the whole API which is scattered in multiple artifacts / packages / and even
projects is deprecated.
Deprecation is technical way to communicate informations to users. And we need
to communicate clearly our intent. I'm fine with undeprecating the Maven 3
API in Maven 4, and make it deprecated when we release the new API. But in
all cases, we need to communicate to users that it will be deprecated in the
coming months. And imho, that kinda means it's already deprecated, but with no
replacement *yet*.
> 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)
