<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Atomicity</title>
	<atom:link href="http://atomicityltd.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://atomicityltd.com</link>
	<description>Technology, Programming and Learning</description>
	<lastBuildDate>Sat, 19 May 2012 07:27:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Ivy and Maven Caching by matt</title>
		<link>http://atomicityltd.com/blog/ivy-and-maven-caching#comment-88</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Sat, 19 May 2012 07:27:28 +0000</pubDate>
		<guid isPermaLink="false">http://atomicityltd.com/?p=29#comment-88</guid>
		<description>The solution I refer to basically looks like this; All Play commands are replaced with a Maven command, e.g. &quot;play deps&quot; becomes &quot;mvn play:deps&quot;. All dependencies are defined in a pom.xml, including the Play framework itself. There is no installation of Play on the target machine. To create a project in an IDE all that is required is the import of the pom.xml, no manual configuration.

In short, the Python scripts are completely replaced by a Maven mojo. Within the corporate environment in which I work this is the only practical way in which we could move forward with the adoption of Play.</description>
		<content:encoded><![CDATA[<p>The solution I refer to basically looks like this; All Play commands are replaced with a Maven command, e.g. &#8220;play deps&#8221; becomes &#8220;mvn play:deps&#8221;. All dependencies are defined in a pom.xml, including the Play framework itself. There is no installation of Play on the target machine. To create a project in an IDE all that is required is the import of the pom.xml, no manual configuration.</p>
<p>In short, the Python scripts are completely replaced by a Maven mojo. Within the corporate environment in which I work this is the only practical way in which we could move forward with the adoption of Play.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ivy and Maven Caching by Grzegorz Slowikowski</title>
		<link>http://atomicityltd.com/blog/ivy-and-maven-caching#comment-87</link>
		<dc:creator>Grzegorz Slowikowski</dc:creator>
		<pubDate>Fri, 18 May 2012 06:34:07 +0000</pubDate>
		<guid isPermaLink="false">http://atomicityltd.com/?p=29#comment-87</guid>
		<description>Hi Matt

I&#039;ve just found this blog. I&#039;m interested in yours &quot;pure Maven solution&quot;.

I&#039;m the author of Maven plugin for Play! Framework (http://code.google.com/p/maven-play-plugin/). 
It supports Play 1.x.</description>
		<content:encoded><![CDATA[<p>Hi Matt</p>
<p>I&#8217;ve just found this blog. I&#8217;m interested in yours &#8220;pure Maven solution&#8221;.</p>
<p>I&#8217;m the author of Maven plugin for Play! Framework (<a href="http://code.google.com/p/maven-play-plugin/" rel="nofollow">http://code.google.com/p/maven-play-plugin/</a>).<br />
It supports Play 1.x.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Custom serialization using Jackson by matt</title>
		<link>http://atomicityltd.com/blog/jackson-custom-serialization#comment-37</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Thu, 12 Jan 2012 06:08:49 +0000</pubDate>
		<guid isPermaLink="false">http://atomicityltd.com/?p=67#comment-37</guid>
		<description>It turns out that there is a way of using annotations to achieve this. It&#039;s not as flexible (or powerful) as the method I described in this post but it&#039;s certainly nicer to look at and easier to configure. The annotations I&#039;m talking about are Mixin Annotations and details can be found here: http://wiki.fasterxml.com/JacksonMixInAnnotations</description>
		<content:encoded><![CDATA[<p>It turns out that there is a way of using annotations to achieve this. It&#8217;s not as flexible (or powerful) as the method I described in this post but it&#8217;s certainly nicer to look at and easier to configure. The annotations I&#8217;m talking about are Mixin Annotations and details can be found here: <a href="http://wiki.fasterxml.com/JacksonMixInAnnotations" rel="nofollow">http://wiki.fasterxml.com/JacksonMixInAnnotations</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

