<div id="midcolumn">
	<h2>The History of Gemini Blueprint</h2>
	<p>
		The Gemini Blueprint project started life at the end of 2006 as the Spring OSGi project. 
		Later it was renamed to the Spring Dynamic Modules that many people know today. 
		Gemini Blueprint shares many goals with Spring DM such as:
	</p>
	<ul>
		<li>Better OSGi platform</li>
		<li>Advanced IoC container capabilities</li>
		<li>Lightweight, trasparent, POJO-based programming model</li>
	</ul>
	<p>
		Spring DM combined the powerful model offered by Spring <a href="www.springframework.org">Framework</a>
		with the dynamic and modular capabilities of the OSGi platform. The combination proved so successful
		and popular that the OSGi Alliance decided to standardise this programming model through the
		OSGi Service Blueprint, as part of the OSGi Compendium Services <a href="http://www.osgi.org/News/20090924">4.2</a> 
		release.
	</p>
	<p>
		In late 2009, Spring DM became its transition to Eclipse through the Gemini project <a href="http://eclipse.org/proposals/gemini/">proposal</a>.
	</p>
	<p>
		At the time of writing, we are still working on the transition - we'll be sure to update the project page and
		spread the news as soon as this process completes.
	</p>

</div>