Skip to main content

When should an optional package be deprecated?

When active development ends
13% (43 votes)
When maintenance development ends
31% (102 votes)
When it won't work with a new J2SE
44% (148 votes)
12% (40 votes)
Total votes: 333


Keep it fit!

Simply keep it fit, up-to-date, easy to use and logical (and avoid bugs)!

don't just deprecate, cull

it's high time that packages that were deprecated years ago be completely removed. Keep them for a cycle, maybe even two, for people to have time to remove references to them, then mercilessly cull them from the codebase. Might need to add an Exception for this, "DeprecatedMethodCallException" extends RuntimeException (or maybe Error).

When nobody uses it OR when a better alternative is available.

Otherwise, never. If maintainance stops; better open source the optional package.