<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="0.92">
<channel>
	<title>Labora</title>
	<link>http://labora.harnvi.net</link>
	<description>Markus blogs about work, Java, Open Source and other things that his friends and family hate to read about on his personal blog...</description>
	<lastBuildDate>Fri, 30 Oct 2009 11:05:56 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Bad news for Netbeans?</title>
		<description>The latest document from Oracle on the merger doesn't look that good for Netbeans. Glassfish will get resources and be more integrated with Weblogic. MySQL will get more resources. Solaris, Sparc, storage too.

But for Netbeans:

"As such, NetBeans is expected to provide an additional open 
source option". No commitment. 

More at ...</description>
		<link>http://labora.harnvi.net/?p=80</link>
			</item>
	<item>
		<title>Docbook, Maven, SVG and fonts</title>
		<description>I wrote in my last post about using Maven to build good-looking and maintainable documentation. I had issues with raster images getting rendered in the wrong resolution with Apache FOP. I tried RenderX XEP and it rendered in the correct resolution, but the images still look a bit blurred in ...</description>
		<link>http://labora.harnvi.net/?p=79</link>
			</item>
	<item>
		<title>Docbook and Apache FOP</title>
		<description>I have taken up Docbook again. It was too much configuration and fixing when I tried it a few years ago. But now I found a Maven plugin that makes it really easy. Fonts go in one directory, custom XSL in another, images and docbook files in a third. Then ...</description>
		<link>http://labora.harnvi.net/?p=78</link>
			</item>
	<item>
		<title>SpringSource fixes policy</title>
		<description>Good stuff!
 </description>
		<link>http://labora.harnvi.net/?p=77</link>
			</item>
	<item>
		<title>Opening in the Spring conflict?</title>
		<description>On the end of the TSS thread Rod Johnson seems to be willing to consider a compromise with the Spring community. 

The suggestion put out by Greg Matthews was that SpringSource would provide tags on maintenance releases only for the most current major version of Spring. So when Spring 3.0 ...</description>
		<link>http://labora.harnvi.net/?p=76</link>
			</item>
	<item>
		<title>New Spring policy: maintenance branch to the rescue?</title>
		<description>I listened to Alef Arendsen in Stockholm today and he said that the problem for non-customers could be solved by using the maintenance branch.

If you checkout from the maintenance branch you can follow what issues have been fixed by cross referencing with the Jira issues. You will not get unfinished ...</description>
		<link>http://labora.harnvi.net/?p=75</link>
			</item>
	<item>
		<title>The SpringSource FAQ makes it even worse</title>
		<description>Now SpringSource have published an FAQ about the license change (yes, it is a license change). Spring will be dual licensed. The source tree will be using ASF and be considered Open Source. It will not have tags for maintenance releases. There is no way to get bug fixes three ...</description>
		<link>http://labora.harnvi.net/?p=73</link>
			</item>
	<item>
		<title>Best summary of the problem with SpringSource new policy</title>
		<description>I wrote about it here, but Alessandro Santini is explaining it better here.

It's not about SpringSource making money - I hope they all get stinking rich. It's not demanding that all software should be free. But it is about blurring the line between closed source and Open Source. And I ...</description>
		<link>http://labora.harnvi.net/?p=72</link>
			</item>
	<item>
		<title>Dark clouds over Spring</title>
		<description>Rod Johnson writes:

Source code will be published in the source repository. After 3 months SpringSource will continue make maintenance releases as needed to support our customers. There will be no tags in the repository corresponding to those releases. 

Rod says in a clarification that the new policy "only affects those ...</description>
		<link>http://labora.harnvi.net/?p=71</link>
			</item>
	<item>
		<title>Groovy on NetBeans again</title>
		<description>I tried installing Groovy support in Netbeans 6.1 on Windows and failed. I tried again on my Mac today but got this:



Should I stop trying? There where a lot of blog posts about Groovy support in NetBeans 6.1 before it was released, but is it really a supported feature?  </description>
		<link>http://labora.harnvi.net/?p=70</link>
			</item>
</channel>
</rss>
