<?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: Publishing to Maven Central Repo in 5 steps</title>
	<atom:link href="http://www.vineetmanohar.com/2009/12/publishing-to-maven-central-repo-in-5-steps/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vineetmanohar.com/2009/12/publishing-to-maven-central-repo-in-5-steps/</link>
	<description>Java, Web 2.0 and other Tech topics</description>
	<lastBuildDate>Thu, 02 Sep 2010 15:16:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Brian Fox</title>
		<link>http://www.vineetmanohar.com/2009/12/publishing-to-maven-central-repo-in-5-steps/comment-page-1/#comment-4302</link>
		<dc:creator>Brian Fox</dc:creator>
		<pubDate>Wed, 10 Feb 2010 01:54:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.vineetmanohar.com/?p=680#comment-4302</guid>
		<description>Hi Vineet,
For the short term the rsyncs will be continued but we will encourage people to switch and gain the benefits of automatic verification in the forges. Over the long term, we hope to reduce the rsyncs to just the forges. 

The other benefit I forgot to mention about this strategy is it becomes more of a push model for releases via the forges and thus things can get into Central much faster. For example, the 3 forges listed on my link above all sync hourly instead of daily like everything else since there&#039;s so much less overhead.

--Brian</description>
		<content:encoded><![CDATA[<p>Hi Vineet,<br />
For the short term the rsyncs will be continued but we will encourage people to switch and gain the benefits of automatic verification in the forges. Over the long term, we hope to reduce the rsyncs to just the forges. </p>
<p>The other benefit I forgot to mention about this strategy is it becomes more of a push model for releases via the forges and thus things can get into Central much faster. For example, the 3 forges listed on my link above all sync hourly instead of daily like everything else since there&#8217;s so much less overhead.</p>
<p>&#8211;Brian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vineet</title>
		<link>http://www.vineetmanohar.com/2009/12/publishing-to-maven-central-repo-in-5-steps/comment-page-1/#comment-4300</link>
		<dc:creator>vineet</dc:creator>
		<pubDate>Tue, 09 Feb 2010 21:37:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.vineetmanohar.com/?p=680#comment-4300</guid>
		<description>Hi Brian, 

Will the old rsyncs for individual projects be maintained?

Thanks,
Vineet</description>
		<content:encoded><![CDATA[<p>Hi Brian, </p>
<p>Will the old rsyncs for individual projects be maintained?</p>
<p>Thanks,<br />
Vineet</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Fox</title>
		<link>http://www.vineetmanohar.com/2009/12/publishing-to-maven-central-repo-in-5-steps/comment-page-1/#comment-4299</link>
		<dc:creator>Brian Fox</dc:creator>
		<pubDate>Tue, 09 Feb 2010 21:31:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.vineetmanohar.com/?p=680#comment-4299</guid>
		<description>The rsync process over the years has grown to become unmaintainable. It&#039;s not efficient to reach out twice a day to thousands of servers to pick up artifacts that on average change only a few times a year. Keeping all the syncs updated when people change servers etc has grown to an enormous effort.

Additionally, one of the major rants against Maven is the quality of the metadata in Central. Unfortunately the trash that gets in there is almost always coming from these rsynced in projects because there&#039;s no good way to validate it.

Because of this, the rsyncs are no longer being added for individual projects, only for large forges that host many projects, or very large and active projects by exception. These new forges and syncs must meet much more stringent criteria and this goes to help all Maven users by stopping the garbage at the front door.

The &lt;a href=&quot;http://maven.apache.org/guides/mini/guide-central-repository-upload.html&quot; rel=&quot;nofollow&quot;&gt;Guide&lt;/a&gt; has been updated to reflect this policy change that took effect this year.

--Brian Fox
Apache Maven PMC Chair</description>
		<content:encoded><![CDATA[<p>The rsync process over the years has grown to become unmaintainable. It&#8217;s not efficient to reach out twice a day to thousands of servers to pick up artifacts that on average change only a few times a year. Keeping all the syncs updated when people change servers etc has grown to an enormous effort.</p>
<p>Additionally, one of the major rants against Maven is the quality of the metadata in Central. Unfortunately the trash that gets in there is almost always coming from these rsynced in projects because there&#8217;s no good way to validate it.</p>
<p>Because of this, the rsyncs are no longer being added for individual projects, only for large forges that host many projects, or very large and active projects by exception. These new forges and syncs must meet much more stringent criteria and this goes to help all Maven users by stopping the garbage at the front door.</p>
<p>The <a href="http://maven.apache.org/guides/mini/guide-central-repository-upload.html" rel="nofollow">Guide</a> has been updated to reflect this policy change that took effect this year.</p>
<p>&#8211;Brian Fox<br />
Apache Maven PMC Chair</p>
]]></content:encoded>
	</item>
</channel>
</rss>
