<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Sonatype Blog &#187; Hudson Professional</title>
	<atom:link href="http://blog.sonatype.com/people/tag/hudson-professional/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sonatype.com/people</link>
	<description>Sonatype is transforming software development with tools, information and services that enable organizations to build better software, faster, using open-source components.</description>
	<lastBuildDate>Tue, 18 Jun 2013 15:30:05 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Hudson Pro: Where’s the Maven job type?</title>
		<link>http://blog.sonatype.com/people/2011/05/hudson-pro-where%e2%80%99s-the-maven-job-type/</link>
		<comments>http://blog.sonatype.com/people/2011/05/hudson-pro-where%e2%80%99s-the-maven-job-type/#comments</comments>
		<pubDate>Tue, 03 May 2011 13:00:46 +0000</pubDate>
		<dc:creator>Tim O'Brien</dc:creator>
				<category><![CDATA[Hudson]]></category>
		<category><![CDATA[Maven]]></category>
		<category><![CDATA[Hudson Professional]]></category>

		<guid isPermaLink="false">http://www.sonatype.com/people/?p=8041</guid>
		<description><![CDATA[One important difference between Hudson Open Source and Hudson Professional is how they support Maven 3. Sonatype has developed state-of-the-art support for Maven 3 focusing on creating seamless integration between the internals of Hudson CI and Maven.   Year of work on Maven 3 internals to support more efficient embedding along with our multi-year investment in [...]]]></description>
				<content:encoded><![CDATA[<p>One important difference between Hudson Open Source and Hudson Professional is how they support Maven 3.</p>

<p>Sonatype has developed state-of-the-art  support for Maven 3 focusing on creating seamless integration between  the internals of Hudson CI and Maven.   Year of work on Maven 3  internals to support more efficient embedding along with our multi-year  investment in bringing both JSR-330 support and GWT UI integration to  Hudson CI  has produced a CI system that support Maven 3 like no other  on the market.</p>

<p>If  you’ve used Hudson and Maven together in the past, you might be  familiar with the Maven 2 project type that provides users with the  ability to define a Maven build that is aware of a project’s POM. While we understood the motivation for a Maven-specific project type,  we took our Maven support in an entirely difference direction. We  created a Maven build that can be used a part of a larger freestyle  build, and the reason we did this was to get away for the idea that a  Maven build can only include one step, one call to a series of goals.</p>

<p>Sonatype found this to be more of a limitation than an advantage.</p>

<p><span id="more-8041"></span></p>

<p><strong>Supporting Real-world Maven Builds</strong></p>

<p>Why?   Consider an enterprise build &#8211; one that needs to prepare and perform a  release.  In the scenario it is essential that the build process  contain two separate calls to release:prepare and release:perform. It  also might be essential to call out to supporting scripts or other parts  of the build that might fall outside of the scope of the Maven build. In a complex build environment, Maven is often not the only build tool  involved in a process. Instead of binding our users to a single  Maven-specific project type, we implemented Maven support as a builder  to make sure that Hudson Professional users had as much flexibility as  they needed to create quality enterprise builds.</p>

<p><strong>Creating a New Maven 3 Job</strong>
If  you are new to Hudson Professional and you are wondering how to create a  new Maven 3 build, you should follow these simple steps:</p>

<ol>
<li>Create a New Job</li>
<li>Select “Build a free-style Software Project”</li>
<li>Add a Build Step and select “Invoke” Maven.</li>
</ol>

<p><strong>Creating a New Maven 3 Project from a Git Repository</strong></p>

<p>The following video demonstrates the process for creating a new Maven 3 project from a Git repository:</p>

<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="600" height="371" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/Mh7ft61Wg9w?fs=1&amp;hl=en_US&amp;rel=0" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="600" height="371" src="http://www.youtube.com/v/Mh7ft61Wg9w?fs=1&amp;hl=en_US&amp;rel=0" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>

<p><strong>Creating a New Maven 3 Project from a Subversion Repository</strong></p>

<p>The following video demonstrates the process for creating a new Maven 3 project from a Subversion repository:</p>

<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="600" height="371" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/1-tgRMm_Qo0?fs=1&amp;hl=en_US&amp;rel=0" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="600" height="371" src="http://www.youtube.com/v/1-tgRMm_Qo0?fs=1&amp;hl=en_US&amp;rel=0" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.sonatype.com/people/2011/05/hudson-pro-where%e2%80%99s-the-maven-job-type/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
