<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Publish globally, trust locally</title>
	<link>http://tech.puredanger.com/2008/03/27/publish-globally-trust-locally/</link>
	<description>Alex Miller's technical blog</description>
	<pubDate>Thu, 08 Jan 2009 21:15:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Fred</title>
		<link>http://tech.puredanger.com/2008/03/27/publish-globally-trust-locally/#comment-35542</link>
		<pubDate>Sun, 30 Mar 2008 12:47:27 +0000</pubDate>
		<guid>http://tech.puredanger.com/2008/03/27/publish-globally-trust-locally/#comment-35542</guid>
					<description>@Yardena - Artifactory does the job indeed

About Maven in general, it's like democracy: &quot;It's not perfect but that the best we got!&quot;</description>
		<content:encoded><![CDATA[<p>@Yardena - Artifactory does the job indeed</p>
<p>About Maven in general, it&#8217;s like democracy: &#8220;It&#8217;s not perfect but that the best we got!&#8221;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Alex</title>
		<link>http://tech.puredanger.com/2008/03/27/publish-globally-trust-locally/#comment-35113</link>
		<pubDate>Fri, 28 Mar 2008 15:10:03 +0000</pubDate>
		<guid>http://tech.puredanger.com/2008/03/27/publish-globally-trust-locally/#comment-35113</guid>
					<description>@Scott - agreed.

@Rob - I don't know for sure, but Michael may be referring to Gant, which is Groovy+Ant.  This would be near the top of my list to try if I were going to create a build system from scratch today.  Rake is maybe a similar idea but using Ruby.

@anjan - one thing it gives you is a &quot;standard&quot; build workflow and set of commands for initiating that workflow.  I think bringing regularity to builds across projects and companies is great.  I'm a fan from a concept point of view.  From an execution point of view, Maven is a mixed bag. 

@Jason - thanks for the info.  I'm not sure these best practices are as wide-spread as they should be based on what I've heard. :)

@Tuomas - I'd never heard of P2 before but it seems a little more focused on taking installable things and installing them across a bunch of machines.  I'd consider the build process to be more how those installable things are created in the first place.  But maybe I misjudged P2 based on a quick reading.</description>
		<content:encoded><![CDATA[<p>@Scott - agreed.</p>
<p>@Rob - I don&#8217;t know for sure, but Michael may be referring to Gant, which is Groovy+Ant.  This would be near the top of my list to try if I were going to create a build system from scratch today.  Rake is maybe a similar idea but using Ruby.</p>
<p>@anjan - one thing it gives you is a &#8220;standard&#8221; build workflow and set of commands for initiating that workflow.  I think bringing regularity to builds across projects and companies is great.  I&#8217;m a fan from a concept point of view.  From an execution point of view, Maven is a mixed bag. </p>
<p>@Jason - thanks for the info.  I&#8217;m not sure these best practices are as wide-spread as they should be based on what I&#8217;ve heard. :)</p>
<p>@Tuomas - I&#8217;d never heard of P2 before but it seems a little more focused on taking installable things and installing them across a bunch of machines.  I&#8217;d consider the build process to be more how those installable things are created in the first place.  But maybe I misjudged P2 based on a quick reading.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Yardena</title>
		<link>http://tech.puredanger.com/2008/03/27/publish-globally-trust-locally/#comment-35043</link>
		<pubDate>Fri, 28 Mar 2008 08:56:23 +0000</pubDate>
		<guid>http://tech.puredanger.com/2008/03/27/publish-globally-trust-locally/#comment-35043</guid>
					<description>We've used Artifactory (http://www.jfrog.org/sites/artifactory/latest/) to overcome &quot;download the Internet&quot; problem, it does the job pretty well.</description>
		<content:encoded><![CDATA[<p>We&#8217;ve used Artifactory (http://www.jfrog.org/sites/artifactory/latest/) to overcome &#8220;download the Internet&#8221; problem, it does the job pretty well.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tuomas Kiviaho</title>
		<link>http://tech.puredanger.com/2008/03/27/publish-globally-trust-locally/#comment-35033</link>
		<pubDate>Fri, 28 Mar 2008 07:57:50 +0000</pubDate>
		<guid>http://tech.puredanger.com/2008/03/27/publish-globally-trust-locally/#comment-35033</guid>
					<description>One that belongs to the 'next world' is in my opinion Equinox P2 directed towards provisioning (Eclipse) OSGi bundles.

--
Tuomas</description>
		<content:encoded><![CDATA[<p>One that belongs to the &#8216;next world&#8217; is in my opinion Equinox P2 directed towards provisioning (Eclipse) OSGi bundles.</p>
<p>&#8211;<br />
Tuomas
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jason van Zyl</title>
		<link>http://tech.puredanger.com/2008/03/27/publish-globally-trust-locally/#comment-35004</link>
		<pubDate>Fri, 28 Mar 2008 03:48:13 +0000</pubDate>
		<guid>http://tech.puredanger.com/2008/03/27/publish-globally-trust-locally/#comment-35004</guid>
					<description>Sorry, I didn't mean to post that anonymously. At any rate I was also going to add that publish-globally and trust locally is how Maven was meant to be used from day one, and is in fact, how every corporate client I have uses Maven. Maven's central repository should be used for the initial population of your internal repositories, then all the traffic from your developers to Maven repositories should be internal. The central repository is not the magical forest of artifacts. You should use your own.</description>
		<content:encoded><![CDATA[<p>Sorry, I didn&#8217;t mean to post that anonymously. At any rate I was also going to add that publish-globally and trust locally is how Maven was meant to be used from day one, and is in fact, how every corporate client I have uses Maven. Maven&#8217;s central repository should be used for the initial population of your internal repositories, then all the traffic from your developers to Maven repositories should be internal. The central repository is not the magical forest of artifacts. You should use your own.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
