A group I work with had a requirement to be able to deprecate and ban old versions of their artifacts. The dev team is very large and simply sending out an email telling everyone not to use version 1.0 of some artifact won't work. The team needed a way to warn and/or enforce that the old version is no longer supported and should not (or must not) be used.
I think they started out writing a rule for the Enforcer plugin, but at some point it turned into a separate plugin. (There was a concern about teams simply re-configuring the Enforcer plugin to get around the rules.) In the repository, they have a versions-metadata.xml file sitting next to the maven-metadata.xml file. The plugin examines all the dependencies in the build and looks for the versions-metadata.xml file to see if it needs to warn or fail. They're considering contributing the plugin and are wondering whether it sounds useful to the general Maven community before they start wading through the corporate legal stuff that would be necessary to make that happen. Does it sound like something you might use? Let me know if you want more details on it, or perhaps one of the devs that's involved will chime in. Thanks, -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
