<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for eskatos&#039;s thoughts</title>
	<atom:link href="http://eskatos.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://eskatos.wordpress.com</link>
	<description></description>
	<lastBuildDate>Tue, 19 Jun 2012 20:32:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Unit test JPA Entities with in-memory Derby/JavaDB by Sri</title>
		<link>http://eskatos.wordpress.com/2009/10/26/unit-test-jpa-entities-with-in-memory-derby/#comment-282</link>
		<dc:creator><![CDATA[Sri]]></dc:creator>
		<pubDate>Tue, 19 Jun 2012 20:32:46 +0000</pubDate>
		<guid isPermaLink="false">http://eskatos.wordpress.com/?p=255#comment-282</guid>
		<description><![CDATA[if you have sql-type=&quot;number&quot; in your mapping files, HSQLDB or Derby doesnt like it. either remove it or change it to &quot;numeric&quot;.]]></description>
		<content:encoded><![CDATA[<p>if you have sql-type=&#8221;number&#8221; in your mapping files, HSQLDB or Derby doesnt like it. either remove it or change it to &#8220;numeric&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Unit test JPA Entities with in-memory database by Unit test JPA Entities with in-memory database « Eskatos’s thoughts &#124; linkhalde</title>
		<link>http://eskatos.wordpress.com/2007/10/15/unit-test-jpa-entities-with-in-memory-database/#comment-280</link>
		<dc:creator><![CDATA[Unit test JPA Entities with in-memory database « Eskatos’s thoughts &#124; linkhalde]]></dc:creator>
		<pubDate>Sat, 28 Apr 2012 19:34:53 +0000</pubDate>
		<guid isPermaLink="false">http://eskatos.wordpress.com/2007/10/15/unit-test-jpa-entities-with-in-memory-database/#comment-280</guid>
		<description><![CDATA[[...] Unit test JPA Entities with in-memory database « Eskatos’s thoughts.   This entry was posted in Uncategorized and tagged delicious-import, hibernate, java, jpa, junit, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Unit test JPA Entities with in-memory database « Eskatos’s thoughts.   This entry was posted in Uncategorized and tagged delicious-import, hibernate, java, jpa, junit, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Unit test JPA Entities with in-memory database by Unit test JPA Entities with in-memory database « Eskatos’s thoughts &#124; linkhalde</title>
		<link>http://eskatos.wordpress.com/2007/10/15/unit-test-jpa-entities-with-in-memory-database/#comment-279</link>
		<dc:creator><![CDATA[Unit test JPA Entities with in-memory database « Eskatos’s thoughts &#124; linkhalde]]></dc:creator>
		<pubDate>Sat, 28 Apr 2012 15:04:51 +0000</pubDate>
		<guid isPermaLink="false">http://eskatos.wordpress.com/2007/10/15/unit-test-jpa-entities-with-in-memory-database/#comment-279</guid>
		<description><![CDATA[[...] Unit test JPA Entities with in-memory database « Eskatos’s thoughts.   This entry was posted in Uncategorized and tagged deliciousimport, hibernate, java, jpa, junit, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Unit test JPA Entities with in-memory database « Eskatos’s thoughts.   This entry was posted in Uncategorized and tagged deliciousimport, hibernate, java, jpa, junit, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Quick and dirty howto : Use Hibernate in Glassfish V2 by eskatos</title>
		<link>http://eskatos.wordpress.com/2007/10/09/hello-world/#comment-278</link>
		<dc:creator><![CDATA[eskatos]]></dc:creator>
		<pubDate>Tue, 16 Aug 2011 07:28:53 +0000</pubDate>
		<guid isPermaLink="false">#comment-278</guid>
		<description><![CDATA[See my posts about unit testing with in-memory databases http://eskatos.wordpress.com/2009/10/26/unit-test-jpa-entities-with-in-memory-derby/
You could put two distinct persistence units inside your persistence.xml file, one for production, the other one for tests.
Or, if you use maven (or another build tool you know) you could have one persistence.xml file for production, another one for tests.]]></description>
		<content:encoded><![CDATA[<p>See my posts about unit testing with in-memory databases <a href="http://eskatos.wordpress.com/2009/10/26/unit-test-jpa-entities-with-in-memory-derby/" rel="nofollow">http://eskatos.wordpress.com/2009/10/26/unit-test-jpa-entities-with-in-memory-derby/</a><br />
You could put two distinct persistence units inside your persistence.xml file, one for production, the other one for tests.<br />
Or, if you use maven (or another build tool you know) you could have one persistence.xml file for production, another one for tests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Quick and dirty howto : Use Hibernate in Glassfish V2 by Boris Romashov (@boraldomaster)</title>
		<link>http://eskatos.wordpress.com/2007/10/09/hello-world/#comment-277</link>
		<dc:creator><![CDATA[Boris Romashov (@boraldomaster)]]></dc:creator>
		<pubDate>Thu, 11 Aug 2011 10:47:11 +0000</pubDate>
		<guid isPermaLink="false">#comment-277</guid>
		<description><![CDATA[Thanks for solution, that works in Glassfish now.
But I have one problem.
I hardcode jndi-source in persistence.xml so how can I write unit-test now ?
In unit test I want to create simple datasource (without jndi) and pass it to EntityManager.]]></description>
		<content:encoded><![CDATA[<p>Thanks for solution, that works in Glassfish now.<br />
But I have one problem.<br />
I hardcode jndi-source in persistence.xml so how can I write unit-test now ?<br />
In unit test I want to create simple datasource (without jndi) and pass it to EntityManager.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on flamingo-maven-plugin-1.1 released! by eskatos</title>
		<link>http://eskatos.wordpress.com/2011/06/26/flamingo-maven-plugin-1-1/#comment-274</link>
		<dc:creator><![CDATA[eskatos]]></dc:creator>
		<pubDate>Sun, 26 Jun 2011 12:24:01 +0000</pubDate>
		<guid isPermaLink="false">http://eskatos.wordpress.com/?p=332#comment-274</guid>
		<description><![CDATA[It seems I published this one a little bit too early, the plugin has not hit maven-central yet.
It should be available in a couple hours.]]></description>
		<content:encoded><![CDATA[<p>It seems I published this one a little bit too early, the plugin has not hit maven-central yet.<br />
It should be available in a couple hours.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Unit test JPA Entities with in-memory Derby/JavaDB by Uso de JPA, Hibernate y Derby &#171; Ruben ChT&#039;s Blog</title>
		<link>http://eskatos.wordpress.com/2009/10/26/unit-test-jpa-entities-with-in-memory-derby/#comment-273</link>
		<dc:creator><![CDATA[Uso de JPA, Hibernate y Derby &#171; Ruben ChT&#039;s Blog]]></dc:creator>
		<pubDate>Thu, 19 May 2011 09:05:26 +0000</pubDate>
		<guid isPermaLink="false">http://eskatos.wordpress.com/?p=255#comment-273</guid>
		<description><![CDATA[[...] Configuración de JPA para usar Hibernate [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Configuración de JPA para usar Hibernate [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting used to gradle, a case study : developing Qi4j by eskatos</title>
		<link>http://eskatos.wordpress.com/2011/04/10/gradle-qi4j/#comment-272</link>
		<dc:creator><![CDATA[eskatos]]></dc:creator>
		<pubDate>Mon, 11 Apr 2011 07:41:22 +0000</pubDate>
		<guid isPermaLink="false">http://eskatos.wordpress.com/?p=288#comment-272</guid>
		<description><![CDATA[Hi Niclas,

As you state, I had no real problem with gradle. I&#039;m sure the only problem is me not knowing it enough as from what I understand all that I did here is doable with gradle itself. I wanted to tryout some development workflow without touching a bit of the Qi4j build system.

I tried to put a gradle.properties for the version at the qi4j-sdk root but it&#039;s not used when I&#039;m in the libraries/servlet folder for example.

../libraries/servlet $ gradle install -Dversion=1.3.0-SNAPSHOT

Takes about 50 seconds.

The gradle command my script issue to install only libraries/servlet is

../qi4j-sdk $ gradle -a -x javadoc -x javadocJar -x sourceJar :org.libraries:org.library:servlet install -Dversion=1.3.0-SNAPSHOT

Time goes down to 20 seconds.

In short when I&#039;m working on a module I want to be able to compile and install its jar quickly without updating its source and javadoc artifacts, sometimes even without running its tests (adding -x test).

I applied the very same idea to the whole qi4j-sdk build. Meaning compiling and installing all Qi4j ecosystem artifacts without updating source and javadoc artifacts and without building the distribution archives.

Writing theses scripts I was obviously thinking about porting them into the Qi4j gradle setup once they are proven usefull. If it&#039;s possible to add such a workflow directly in the Qi4j build system that would be awesome.

/Paul]]></description>
		<content:encoded><![CDATA[<p>Hi Niclas,</p>
<p>As you state, I had no real problem with gradle. I&#8217;m sure the only problem is me not knowing it enough as from what I understand all that I did here is doable with gradle itself. I wanted to tryout some development workflow without touching a bit of the Qi4j build system.</p>
<p>I tried to put a gradle.properties for the version at the qi4j-sdk root but it&#8217;s not used when I&#8217;m in the libraries/servlet folder for example.</p>
<p>../libraries/servlet $ gradle install -Dversion=1.3.0-SNAPSHOT</p>
<p>Takes about 50 seconds.</p>
<p>The gradle command my script issue to install only libraries/servlet is</p>
<p>../qi4j-sdk $ gradle -a -x javadoc -x javadocJar -x sourceJar :org.libraries:org.library:servlet install -Dversion=1.3.0-SNAPSHOT</p>
<p>Time goes down to 20 seconds.</p>
<p>In short when I&#8217;m working on a module I want to be able to compile and install its jar quickly without updating its source and javadoc artifacts, sometimes even without running its tests (adding -x test).</p>
<p>I applied the very same idea to the whole qi4j-sdk build. Meaning compiling and installing all Qi4j ecosystem artifacts without updating source and javadoc artifacts and without building the distribution archives.</p>
<p>Writing theses scripts I was obviously thinking about porting them into the Qi4j gradle setup once they are proven usefull. If it&#8217;s possible to add such a workflow directly in the Qi4j build system that would be awesome.</p>
<p>/Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting used to gradle, a case study : developing Qi4j by Niclas Hedhman</title>
		<link>http://eskatos.wordpress.com/2011/04/10/gradle-qi4j/#comment-271</link>
		<dc:creator><![CDATA[Niclas Hedhman]]></dc:creator>
		<pubDate>Mon, 11 Apr 2011 05:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://eskatos.wordpress.com/?p=288#comment-271</guid>
		<description><![CDATA[So, the main &quot;problem&quot; is actually that you want &#039;install&#039; goal, which triggers quite a lot. What time do you get if you do;

cd libraries/servlet
gradlew install -Dversion=1.3.0-SNAPSHOT

??


Also, you can put &quot;version&quot; in a gradle.properties file in the project root, so you don&#039;t need to type that every time.


Further, if you study the dependency graph of goals in gradle, and tell me exactly which custom &#039;fast track&#039; paths you want to take, perhaps we can just create those goals in the build.

The default build is &#039;classes&#039; and &#039;test&#039;, which I consider a minimum.]]></description>
		<content:encoded><![CDATA[<p>So, the main &#8220;problem&#8221; is actually that you want &#8216;install&#8217; goal, which triggers quite a lot. What time do you get if you do;</p>
<p>cd libraries/servlet<br />
gradlew install -Dversion=1.3.0-SNAPSHOT</p>
<p>??</p>
<p>Also, you can put &#8220;version&#8221; in a gradle.properties file in the project root, so you don&#8217;t need to type that every time.</p>
<p>Further, if you study the dependency graph of goals in gradle, and tell me exactly which custom &#8216;fast track&#8217; paths you want to take, perhaps we can just create those goals in the build.</p>
<p>The default build is &#8216;classes&#8217; and &#8216;test&#8217;, which I consider a minimum.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Unit test JPA Entities with in-memory database by Adarsh Pandey</title>
		<link>http://eskatos.wordpress.com/2007/10/15/unit-test-jpa-entities-with-in-memory-database/#comment-270</link>
		<dc:creator><![CDATA[Adarsh Pandey]]></dc:creator>
		<pubDate>Fri, 11 Feb 2011 21:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://eskatos.wordpress.com/2007/10/15/unit-test-jpa-entities-with-in-memory-database/#comment-270</guid>
		<description><![CDATA[nice buddy, keep it up.]]></description>
		<content:encoded><![CDATA[<p>nice buddy, keep it up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
