Jim, 2009/11/17 Jim Barrows <[email protected]>
> > The behavior of a method, it's implementation is part of the contract I > have with the library. > Behavior yes, as long as agreed part of the contract. Implementation no. > So, just because you, or some committee ... > Not a committe, but the developer of the library. > ... think that the change is "minor", I still have to thoroughly test > everything that uses your library. > Did you hear me saying "Don't test your app when a required library changes its version"? > As to your "As Lift also is to support OSGi (already some support in place) > it would be beneficial to stick to this version policy" comment. I counter > with "Lift works on Ubuntu it would be beneficial to stick to this version > policy" and of course "Lift runs on scala it would be beneficial to stick > to this version policy", or better yet "Lift runs on the Java VM it would > be beneficial to stick to this version policy." All three of my arguments > have far more to do with Lift running then OSGI does. > If you are not interested in OSGi or Lift's OSGi support, then just ignore it. As far as I know neither Ubuntu, nor Scala, nor the JVM care about Lift's version number or version strategy. But OSGi does! > That's what I really need to know, > Please accept that other folks might have different needs. Heiko Seeberger My job: weiglewilczek.com My blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=.
