<?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 on: Maven appassembler Plugin: Dealing with Long Classpaths on Windows</title>
	<atom:link href="http://blog.xebia.com/2009/11/22/maven-appassembler-plugin-dealing-with-long-classpath-on-windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xebia.com/2009/11/22/maven-appassembler-plugin-dealing-with-long-classpath-on-windows/</link>
	<description></description>
	<lastBuildDate>Thu, 11 Mar 2010 16:23:01 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alexander</title>
		<link>http://blog.xebia.com/2009/11/22/maven-appassembler-plugin-dealing-with-long-classpath-on-windows/comment-page-1/#comment-93598</link>
		<dc:creator>Alexander</dc:creator>
		<pubDate>Mon, 21 Dec 2009 12:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=3514#comment-93598</guid>
		<description>Looks like you reinvented the wheel</description>
		<content:encoded><![CDATA[<p>Looks like you reinvented the wheel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ShriKant Vashishtha</title>
		<link>http://blog.xebia.com/2009/11/22/maven-appassembler-plugin-dealing-with-long-classpath-on-windows/comment-page-1/#comment-93196</link>
		<dc:creator>ShriKant Vashishtha</dc:creator>
		<pubDate>Mon, 23 Nov 2009 16:16:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=3514#comment-93196</guid>
		<description>assembly plugin can be another way to get away with the long classpath issue. However many people may not want to explode all dependencies in one single jar because of several reasons. The solution mentioned works for them.</description>
		<content:encoded><![CDATA[<p>assembly plugin can be another way to get away with the long classpath issue. However many people may not want to explode all dependencies in one single jar because of several reasons. The solution mentioned works for them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jonas</title>
		<link>http://blog.xebia.com/2009/11/22/maven-appassembler-plugin-dealing-with-long-classpath-on-windows/comment-page-1/#comment-93173</link>
		<dc:creator>jonas</dc:creator>
		<pubDate>Sun, 22 Nov 2009 13:47:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=3514#comment-93173</guid>
		<description>What about just using the assembly plugin with the the jar-with-dependencies output descriptor which will explode all dependencies for you inside the assembled jar? What&#039;s the point of having externalized dependencies in separate .jar files? If you need to keep configuration files external just add the &quot;etc&quot; directory to the class path, e.g. java -cp ./etc:myproject-jar-with-dependecies.jar com.MainClass</description>
		<content:encoded><![CDATA[<p>What about just using the assembly plugin with the the jar-with-dependencies output descriptor which will explode all dependencies for you inside the assembled jar? What&#8217;s the point of having externalized dependencies in separate .jar files? If you need to keep configuration files external just add the &#8220;etc&#8221; directory to the class path, e.g. java -cp ./etc:myproject-jar-with-dependecies.jar com.MainClass</p>
]]></content:encoded>
	</item>
</channel>
</rss>
