<?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: Tips for Successful PDE Product Builds</title>
	<atom:link href="http://eclipsesource.com/blogs/2009/11/07/pde-product-build-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://eclipsesource.com/blogs/2009/11/07/pde-product-build-tips/</link>
	<description>Eclipse Equinox OSGi</description>
	<lastBuildDate>Fri, 03 Feb 2012 14:17:31 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Scott Kovatch</title>
		<link>http://eclipsesource.com/blogs/2009/11/07/pde-product-build-tips/comment-page-1/#comment-3365</link>
		<dc:creator>Scott Kovatch</dc:creator>
		<pubDate>Thu, 04 Feb 2010 17:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://eclipsesource.com/blogs/?p=3332#comment-3365</guid>
		<description>Regarding point 2, if you do have platform-specific fragments, also be sure to build with explicit configs (for example, &quot;configs=macosx, carbon, x86 &amp; win32, win32, x86) in your build.properties. Wildcard specifiers play havoc with generation of fetch scripts, and as a result your platform-specific fragments won&#039;t be copied into the source area for the build.</description>
		<content:encoded><![CDATA[<p>Regarding point 2, if you do have platform-specific fragments, also be sure to build with explicit configs (for example, &#8220;configs=macosx, carbon, x86 &amp; win32, win32, x86) in your build.properties. Wildcard specifiers play havoc with generation of fetch scripts, and as a result your platform-specific fragments won&#8217;t be copied into the source area for the build.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Halverson</title>
		<link>http://eclipsesource.com/blogs/2009/11/07/pde-product-build-tips/comment-page-1/#comment-3213</link>
		<dc:creator>Ian Halverson</dc:creator>
		<pubDate>Tue, 08 Dec 2009 19:04:26 +0000</pubDate>
		<guid isPermaLink="false">http://eclipsesource.com/blogs/?p=3332#comment-3213</guid>
		<description>Have been working away for hours and then I found your tips --I took in consideration point 3 and 5 in my project and everything works beautifully now. Thank you!</description>
		<content:encoded><![CDATA[<p>Have been working away for hours and then I found your tips &#8211;I took in consideration point 3 and 5 in my project and everything works beautifully now. Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Röck</title>
		<link>http://eclipsesource.com/blogs/2009/11/07/pde-product-build-tips/comment-page-1/#comment-3066</link>
		<dc:creator>Stefan Röck</dc:creator>
		<pubDate>Tue, 10 Nov 2009 11:31:56 +0000</pubDate>
		<guid isPermaLink="false">http://eclipsesource.com/blogs/?p=3332#comment-3066</guid>
		<description>I ran into point 4 (redundancy between feature and launch config) multiple times. Wouldn&#039;t it make sense to have an option in the launch config to take the bundle list directly from a feature.xml (present in the current workspace)? Using this, missing dependencies could be found earlier.</description>
		<content:encoded><![CDATA[<p>I ran into point 4 (redundancy between feature and launch config) multiple times. Wouldn&#8217;t it make sense to have an option in the launch config to take the bundle list directly from a feature.xml (present in the current workspace)? Using this, missing dependencies could be found earlier.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

