<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: @license and @copyright in Java 7 ?</title>
	<link>http://stephan.reposita.org/archives/2007/11/04/license-and-copyright-in-java-7/</link>
	<description>Productivity in software development</description>
	<pubDate>Sun, 12 Oct 2008 23:47:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: Geoffrey Wiseman</title>
		<link>http://stephan.reposita.org/archives/2007/11/04/license-and-copyright-in-java-7/#comment-37447</link>
		<dc:creator>Geoffrey Wiseman</dc:creator>
		<pubDate>Tue, 06 Nov 2007 00:00:18 +0000</pubDate>
		<guid>http://stephan.reposita.org/archives/2007/11/04/license-and-copyright-in-java-7/#comment-37447</guid>
		<description>I was thinking of an @License annotation the other day; what I'd really love is the ability to report on the @License of a project and its dependencies, and, ideally, establish some rules about it, and put that into a Maven plugin or something equally re-usable.

For instance, if you're building a commercial application, you might want to exclude GPL dependencies, or generate a report that can be reviewed regularly to ensure that you meet some license compliance goals.</description>
		<content:encoded><![CDATA[<p>I was thinking of an @License annotation the other day; what I&#8217;d really love is the ability to report on the @License of a project and its dependencies, and, ideally, establish some rules about it, and put that into a Maven plugin or something equally re-usable.</p>
<p>For instance, if you&#8217;re building a commercial application, you might want to exclude GPL dependencies, or generate a report that can be reviewed regularly to ensure that you meet some license compliance goals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stephan</title>
		<link>http://stephan.reposita.org/archives/2007/11/04/license-and-copyright-in-java-7/#comment-37347</link>
		<dc:creator>stephan</dc:creator>
		<pubDate>Mon, 05 Nov 2007 09:26:59 +0000</pubDate>
		<guid>http://stephan.reposita.org/archives/2007/11/04/license-and-copyright-in-java-7/#comment-37347</guid>
		<description>Thought about that, but it's neither about defect prevention (JSR 305) nor about new places for annotations (JSR 308). But it should be a good idea to talk to the leads. Thanks.</description>
		<content:encoded><![CDATA[<p>Thought about that, but it&#8217;s neither about defect prevention (JSR 305) nor about new places for annotations (JSR 308). But it should be a good idea to talk to the leads. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Colebourne</title>
		<link>http://stephan.reposita.org/archives/2007/11/04/license-and-copyright-in-java-7/#comment-37346</link>
		<dc:creator>Stephen Colebourne</dc:creator>
		<pubDate>Mon, 05 Nov 2007 09:21:29 +0000</pubDate>
		<guid>http://stephan.reposita.org/archives/2007/11/04/license-and-copyright-in-java-7/#comment-37346</guid>
		<description>You should probably chat to JSR-305/JSR-308 first before thinking about a new JSR.</description>
		<content:encoded><![CDATA[<p>You should probably chat to JSR-305/JSR-308 first before thinking about a new JSR.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
