Hi Paul, The framework is the thing which provides all the nice core OSGi stuff. It is only referred to by the launchpad stuff.
There have been numerous fixes in the framework since the 1.0.4 release. So to keep up with the current developments (most notably fragment support but also enhanced performance and better error messages in the class loading area are certainly worth the move. Hope this helps. Regards Felix Paul Noden schrieb: > Hey Felix, > > Why should we upgrade the dependency if the release isn't dependent? I > guess your concern is in ensuring this release is an easy to use - > future thinking - stable release? > > Presumably for the binary distributions of the release we can include > any version which meets the project's dependencies, such as a stable > and up-to-date version like 1.2.1... For fresh builds Maven ought to > use the latest version if not otherwise specified. > > This means that the current situation seems to meet our requirements > whilst leaving the opportunity for building the release for use with < > 1.2.1 ? > > This is therefore a decision which the code dictates, and I'm the > first one to admit that I've not gotten around to actually committing > code to this project (yet) - perhaps you're already running up against > use cases for 1.2.1 in which case this is an easy +1 for when those > use cases get committed. Otherwise could you provide some additional > reasoning for those of us a little distanced from the coding? > > Paul Noden >
