--
View this message in context:
http://www.nabble.com/Deprecating-and-banning-artifacts-with-repository-metadata-tp25391001p25427364.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
Hi,
FYI I've created a ticket few months ago to create such Sonar plugin :
http://jira.codehaus.org/browse/SONARPLUGINS-41.
This Sonar plugin could work like this :
1 - Accept a text list of prohibited dependencies. For instance :
It sounds like it could be useful, but perhaps with a warning as there are
maintenance projects applying bug fixes to existing projects that may not want
to update older components to avoid too many changes.
Ben
On 10/09/2009 22:03, Wendy Smoak wsm...@gmail.com wrote:
A group I work with
Sounds useful to me.
We were going to build a similar plugin - but the plan for it to be a sonar
plugin rather than a maven plugin.
Jim
On Fri, Sep 11, 2009 at 10:23 AM, Ben Lidgey blid...@movenetworks.comwrote:
It sounds like it could be useful, but perhaps with a warning as there are
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
