codewithsinchana commented on issue #10134: URL: https://github.com/apache/maven/issues/10134#issuecomment-6505265916
Hi Maven maintainers, I'd like to contribute to this issue as part of my work on Apache Maven. My understanding is that the proposal is to introduce a deprecation flag and an optional message in the Maven 4.1.0 model, allowing project maintainers to communicate that a project is no longer maintained or has been deprecated. Before starting implementation, I'd like to clarify the intended model structure and expected behavior. Should this be limited to representing the deprecation metadata in the POM, or should Maven also surface warnings when a deprecated project is used as a dependency? I'm happy to investigate the existing relocation model and propose an implementation consistent with Maven's model and validation conventions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
