-1 it is used in war and ear plugins
also we can find https://github.com/search?q=%22%3CartifactId%3Emaven-mapping%3C%2FartifactId%3E%22+language%3A%22Maven+POM%22++NOT+is%3Aarchived&type=code&l=Maven+POM https://github.com/search?q=import++org.apache.maven.shared.mapping++NOT+is%3Aarchived&type=code On Tue, 15 Jul 2025 at 20:15, Matthias Bünger <mbuen...@apache.org> wrote: > > Hi everyone, > during migration from JIRA to GitHub we noticed that the mentioned > component is no longer used, but was not yet archived. While (in > difference to plugins) there is no strict plan how to retire components, > but the current state of the component says the differnt, meaning that > > * the componenent is listd as active on site > * the JIRA component is listed as "active" > * the GitHub repository is not archived > * the readme of the GitHub repository gives no information about the > deprecation [1] > * there is no retirement task/issue > > To have a clear migration and be able to set the affected JIRA project > to read-only we need to decide how to move on with this component. > My suggestion is to take minimal efforts to archive it. This means > > * set the componend to inactive on site and in the JIRA project, > * ask INFRA to proper archive the repository, and > * of course finish retirement issue > > What do you think? > > Matthias > > > [1] https://github.com/apache/maven-mapping > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Sławomir Jaranowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
