[gatein-dev] New jboss-parent pom

[Arnaud HERITIER]

Hi,

   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="
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#arguments

  Thus in the case of gatein portal where arguments is already set to
"-Prelease,pkg-tomcat,pkg-jbossas
-Dmaven.test.skip=true" in its parent pom (
https://svn.jboss.org/repos/gatein/portal/trunk/pom.xml)
  the command line to use is :
  mvn release:perform -Darguments="-Prelease,pkg-tomcat,pkg-jbossas
-Dmaven.test.skip=true -Djboss.releases.repo.url
=file://THE_PATH_OF_YOUR_LOCAL_CHECKOUT"

  Sorry for the problem it created in the release of the beta3.

  Cheers,

Arnaud Héritier
Software Factory Manager
eXo platform - http://www.exoplatform.com
---
http://www.aheritier.net


On Thu, Nov 19, 2009 at 6:25 PM, Arnaud HERITIER <
arnaud.heritier at exoplatform.com> wrote:

> Hi all,
>
>   I just released a new Jboss parent pom (5-beta-5) with following changes
> :
>
> [JBBUILD-567 <https://jira.jboss.org/jira/browse/JBBUILD-567>] - Add
> properties in distributionManagement URLs to allow to override them
> [JBBUILD-569 <https://jira.jboss.org/jira/browse/JBBUILD-569>] -
> jboss-parent POM should include wagon-webdav configuration
> [JBBUILD-571 <https://jira.jboss.org/jira/browse/JBBUILD-571>] - Add sonar
> plugin in pluginManagement
> [JBBUILD-572 <https://jira.jboss.org/jira/browse/JBBUILD-572>] - Upgrade
> maven-checkstyle-plugin 2.3 -> 2.4
> [JBBUILD-573 <https://jira.jboss.org/jira/browse/JBBUILD-573>] - Upgrade
> maven-ear-plugin 2.3.2 -> 2.4
> [JBBUILD-574 <https://jira.jboss.org/jira/browse/JBBUILD-574>] - Upgrade
> maven-javadoc-plugin 2.6 -> 2.6.1
> [JBBUILD-575 <https://jira.jboss.org/jira/browse/JBBUILD-575>] - Upgrade
> maven-plugin-plugin 2.5 -> 2.5.1
> [JBBUILD-576 <https://jira.jboss.org/jira/browse/JBBUILD-576>] - Upgrade
> maven-resources-plugin 2.4 -> 2.4.1
> [JBBUILD-577 <https://jira.jboss.org/jira/browse/JBBUILD-577>] - Upgrade
> maven-source-plugin 2.1 -> 2.1.1
> [JBBUILD-578 <https://jira.jboss.org/jira/browse/JBBUILD-578>] - Upgrade
> findbugs-maven-plugin 2.1 -> 2.2
>
> What it will change for us ?
>
>   1) Before to deploy snapshots on jboss repo (using webdav), due to a
> Maven bug (in 2.2.1 http://jira.codehaus.org/browse/MNG-4301) we had to
> put those settings to not generate invalid checksums :
>
>     <server>
>       <id>jboss-snapshots</id>
>       <username>AAAAAA</username>
>       <password>BBBBBB</password>
>       <configuration>
>         <httpConfiguration>
>           <put>
>             <params>
>               <param>
>                 <name>http.authentication.preemptive</name>
>                 <value>%b,true</value>
>               </param>
>             </params>
>           </put>
>         </httpConfiguration>
>       </configuration>
>     </server>
>
>   Now it is no more necessary. You have to remove it.
>
>   2) We introduced a property to setup where are deployed releases (and
> snapshots).
>   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.
>   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.
>   You just launch the perform part of the release with the additional
> property jboss.releases.repo.url
>   mvn release:perform -Djboss.releases.repo.url
> =file://THE_PATH_OF_YOUR_LOCAL_CHECKOUT
>   (do not forget the file:// protocol before the path of your repo, it's an
> url)
>   And you commit changes in your local repo.
>   It has also the advantage to be an atomic commit if your release fails.
>
>
>   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 ?
>
>   I'll see also with eXo JCR team to update their parent to use it.
>
> Arnaud Héritier
> Software Factory Manager
> eXo platform - http://www.exoplatform.com
> ---
> http://www.aheritier.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/gatein-dev/attachments/20091130/15f823b4/attachment.html