Jerome Lacoste pisze: > On the Debian package management system (and probably in others) > there's a way to define a package as providing another package's > functionality, allowing superseding of information. > > Could there be a somewhat identical feature in maven which would > enable it to automatically detect that the plugin has now moved > somewhere else? I am not sure how this would fit with the current > implementation and the implicit location of the packages on the remote > repositories. As maven searches in the old location, there would need > to be some sort of link from the old to the new, which somewhat > inverts the dependency between the superseder and deprecated as used > in the deb format. > > Maybe a feature to implement in the repository manager, using some sort of > <overrides> > <override> > <groupId>... > <artifactId>... > <version>[1.0; 3.0(... > </override> > in the overriding POM > > and some backlinks added by the repo manager when the overriding POM > is added to the repository ? > > I would love maven to tell me: warning this dependency is obsolete.
+1000 for this proposal in general. I won't comment technical details as I'm not so much involved in Maven internals. Nevertheless, such option would allow much smoother migration from poorly chosen groupIds and artifactIds as well. -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
