Talk:EquinoxCompatibility
From APIDesign
(Difference between revisions)
(Comment provided by Richard S. Hall - via ArticleComments extension) |
|||
| Line 3: | Line 3: | ||
----- __NOEDITSECTION__</noinclude> | ----- __NOEDITSECTION__</noinclude> | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
== Richard S. Hall said ... == | == Richard S. Hall said ... == | ||
Revision as of 17:54, 14 July 2010
Comments on EquinoxCompatibility <comments />
Follow
I'm not a believer in being backwards compatible with bugs, otherwise there'd be no end. The spec is the law of the land in the OSGi world, so that's what bundles should expect to get. If we weren't strict with that, then bundles would continue to depend on containerisms even after they were corrected.
--Richard S. Hall 03:50, 14 July 2010 (CEST)