Deprecated classes/methods: Add information what to use instead

[Bukama]

New feature, improvement proposal

Several things in org.apache.maven.api.model are marked as deprecated, for example

  @Deprecated(
    since = "4.0.0"
  )
  public String getScriptSourceDirectory() {
    return this.scriptSourceDirectory;
  }

But there is no information what to use instead, resulting in the users (I found it in maven-resource-plugin) only got the deprecated warning, but not hint how to handle it.

[slachiewicz]

While improving 4.x good to backport deprecation advices to 3.x line also to help with migration

[kri-jha]

Hi, I’d like to work on this issue.

I noticed several deprecated APIs in the core/model modules (3.x & 4.x) lack replacement guidance. I can audit these elements and update their JavaDoc with clear “use this instead” information, submitted as small and focused PRs.

Please confirm if this approach aligns with the project’s expectations.

Thank you!