eclipse-sisu / sisu-project

Sisu Inject
https://www.eclipse.org/sisu
Eclipse Public License 2.0
17 stars 15 forks source link

Make component deprecation easier (Bugzilla Bug 388898) #13

Open mcculls opened 2 years ago

mcculls commented 2 years ago

This issue was created automatically with bugzilla2github

Bugzilla Bug 388898

Date: 2012-09-05 21:28:53 -0400 From: Stuart McCulloch <mcculls@gmail.com> To: Project Inbox <sisu-inbox@eclipse.org>

See also: https://issues.sonatype.org/browse/SISU-123 Last updated: 2013-07-16 21:17:03 -0400

Comment 2156608

Date: 2012-09-05 21:28:53 -0400 From: Stuart McCulloch <mcculls@gmail.com>

Migrated from https://issues.sonatype.org/browse/SISU-123

As we know, SISU and it's plexus-shim is here to phase out "oldie" plexus.

Typical case happened with sisu-velocity, it's main role is to drop the use of old plexus-velocity (by providing almost same functionality as plexus-velocity did, smaller enhancements was made + it uses @Inject annotations). It's main use is in Nexus that still uses plexus-shim.

If you take a peek at commit that added back the "deprecated" component (to make sisu-velocity a real drop-in replacement), some of us came up with cool idea: could we have sisu suppport generally for all components at the sisu-level. ie. if the chosen impl for a binding is marked with @deprecated annotations, then complain?

See comments https://github.com/sonatype/sisu-velocity/commit/8f903a3ce66c1413876f39bc08f78776e759e0b6

@jdillon: I'd recommend putting this into sisu-proper and not into any plexus related library, as this is useful going forward for pure jsr-330 components too.