Hi,<div><br></div><div> In this previous mail I made an error. Due to the fact that maven forks itself to launch the deploy task on the tagged source code we have to pass option though "-Darguments="</div><div>
<a href="http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#arguments">http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#arguments</a></div><div><br></div><div> Thus in the case of gatein portal where arguments is already set to "<span class="Apple-style-span" style="font-family: monospace; font-size: medium; white-space: pre-wrap; ">-Prelease,pkg-tomcat,pkg-jbossas -Dmaven.test.skip=true"<span class="Apple-style-span" style="font-family: arial; white-space: normal; font-size: small; "> in its parent pom ( <a href="https://svn.jboss.org/repos/gatein/portal/trunk/pom.xml">https://svn.jboss.org/repos/gatein/portal/trunk/pom.xml</a>)</span></span></div>
<div> the command line to use is :</div><div> mvn release:perform -Darguments="<span class="Apple-style-span" style="font-family: monospace; font-size: medium; white-space: pre-wrap; ">-Prelease,pkg-tomcat,pkg-jbossas -Dmaven.test.skip=true <span class="Apple-style-span" style="font-family: arial, sans-serif; white-space: normal; border-collapse: collapse; font-size: 13px; ">-D<span style="font-family: Monaco; font-size: 11px; "><span class="il" style="background-image: initial; background-repeat: initial; background-attachment: initial; -webkit-background-clip: initial; -webkit-background-origin: initial; "><span class="Apple-style-span" style="background-color: rgb(255, 255, 255);">jboss</span></span>.releases.repo.url<span style="font-family: arial; font-size: small; ">=file://THE_PATH_OF_YOUR_LOCAL_CHECKOUT<span class="Apple-style-span" style="border-collapse: separate; font-family: arial; ">"</span></span></span></span></span></div>
<div> </div><div> Sorry for the problem it created in the release of the beta3.</div><div><br></div><div> Cheers,</div><div><br clear="all">Arnaud Héritier<br>Software Factory Manager<br>eXo platform - <a href="http://www.exoplatform.com">http://www.exoplatform.com</a><br>
---<br><a href="http://www.aheritier.net">http://www.aheritier.net</a><br>
<br><br><div class="gmail_quote">On Thu, Nov 19, 2009 at 6:25 PM, Arnaud HERITIER <span dir="ltr"><<a href="mailto:arnaud.heritier@exoplatform.com">arnaud.heritier@exoplatform.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi all,<div><br></div><div> I just released a new Jboss parent pom (5-beta-5) with following changes :</div><div><br></div><div><span style="font-family:Arial, sans-serif;font-size:12px"><li style="font-family:Arial, sans-serif;font-size:12px;color:black">
[<a href="https://jira.jboss.org/jira/browse/JBBUILD-567" target="_blank">JBBUILD-567</a>] - Add properties in distributionManagement URLs to allow to override them</li><li style="font-family:Arial, sans-serif;font-size:12px;color:black">
[<a href="https://jira.jboss.org/jira/browse/JBBUILD-569" target="_blank">JBBUILD-569</a>] - jboss-parent POM should include wagon-webdav configuration</li><li style="font-family:Arial, sans-serif;font-size:12px;color:black">
[<a href="https://jira.jboss.org/jira/browse/JBBUILD-571" target="_blank">JBBUILD-571</a>] - Add sonar plugin in pluginManagement</li>
<li style="font-family:Arial, sans-serif;font-size:12px;color:black">[<a href="https://jira.jboss.org/jira/browse/JBBUILD-572" target="_blank">JBBUILD-572</a>] - Upgrade maven-checkstyle-plugin 2.3 -> 2.4</li><li style="font-family:Arial, sans-serif;font-size:12px;color:black">
[<a href="https://jira.jboss.org/jira/browse/JBBUILD-573" target="_blank">JBBUILD-573</a>] - Upgrade maven-ear-plugin 2.3.2 -> 2.4</li><li style="font-family:Arial, sans-serif;font-size:12px;color:black">[<a href="https://jira.jboss.org/jira/browse/JBBUILD-574" target="_blank">JBBUILD-574</a>] - Upgrade maven-javadoc-plugin 2.6 -> 2.6.1</li>
<li style="font-family:Arial, sans-serif;font-size:12px;color:black">[<a href="https://jira.jboss.org/jira/browse/JBBUILD-575" target="_blank">JBBUILD-575</a>] - Upgrade maven-plugin-plugin 2.5 -> 2.5.1</li><li style="font-family:Arial, sans-serif;font-size:12px;color:black">
[<a href="https://jira.jboss.org/jira/browse/JBBUILD-576" target="_blank">JBBUILD-576</a>] - Upgrade maven-resources-plugin 2.4 -> 2.4.1</li><li style="font-family:Arial, sans-serif;font-size:12px;color:black">[<a href="https://jira.jboss.org/jira/browse/JBBUILD-577" target="_blank">JBBUILD-577</a>] - Upgrade maven-source-plugin 2.1 -> 2.1.1</li>
<li style="font-family:Arial, sans-serif;font-size:12px;color:black">[<a href="https://jira.jboss.org/jira/browse/JBBUILD-578" target="_blank">JBBUILD-578</a>] - Upgrade findbugs-maven-plugin 2.1 -> 2.2</li></span></div>
<div><br>
</div><div>What it will change for us ?</div><div><br></div><div> 1) Before to deploy snapshots on jboss repo (using webdav), due to a Maven bug (in 2.2.1 <a href="http://jira.codehaus.org/browse/MNG-4301" target="_blank">http://jira.codehaus.org/browse/MNG-4301</a>) we had to put those settings to not generate invalid checksums :</div>
<div><br></div><div><div> <server></div><div> <id>jboss-snapshots</id></div>
<div> <username>AAAAAA</username></div><div> <password>BBBBBB</password></div><div> <configuration></div><div>
<httpConfiguration></div><div> <put></div><div> <params></div><div> <param></div><div> <name>http.authentication.preemptive</name></div>
<div> <value>%b,true</value></div><div> </param></div><div> </params></div><div> </put></div><div> </httpConfiguration></div><div>
</configuration></div><div> </server></div><div><br></div><div> Now it is no more necessary. You have to remove it.</div><div><br></div><div> 2) We introduced a property to setup where are deployed releases (and snapshots).</div>
<div> By default when we release a project Maven is setup with the parent pom to directly publish to the JBoss SVN repository. The problem is that it is slow and thus for big projects it can fails because the upload is too long.</div>
<div> For big projects (or always if you prefer) you can come back to the old solution which is to have a local checkout of the jboss repository.</div><div> You just launch the perform part of the release with the additional property <span style="font-family:Monaco;font-size:11px">jboss.releases.repo.url</span></div>
</div><div> mvn release:perform -D<span style="font-family:Monaco;font-size:11px">jboss.releases.repo.url<span style="font-family:arial;font-size:small">=file://THE_PATH_OF_YOUR_LOCAL_CHECKOUT</span></span></div>
<div> (do not forget the file:// protocol before the path of your repo, it's an url)</div><div> And you commit changes in your local repo.</div><div> It has also the advantage to be an atomic commit if your release fails.</div>
<div><br></div><div><br></div><div> I'll update the gatein parent to use it in few minutes. If you are agree I propose to release the gatein-parent and to update all gatein projects to use it ?</div><div><br></div><div>
I'll see also with eXo JCR team to update their parent to use it.</div><div><br clear="all">Arnaud Héritier<br>Software Factory Manager<br>eXo platform - <a href="http://www.exoplatform.com" target="_blank">http://www.exoplatform.com</a><br>
---<br><a href="http://www.aheritier.net" target="_blank">http://www.aheritier.net</a><br>
</div>
</blockquote></div><br></div>