Hi Peter,<div><br></div><div> Actually I changed nothing on JCR side. We have to see together when I can do it.</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 Mon, Nov 23, 2009 at 9:50 AM, Peter Nedonosko <span dir="ltr"><<a href="mailto:pnedonosko@gmail.com">pnedonosko@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
Arnaud, I ask you to clarify the release process for us (JCR & co).<br>
Can we use existing steps or it's something new for us with those changes?<br>
<br>
Thanks<br>
<font color="#888888">Peter<br>
</font><div><div></div><div class="h5"><br>
On Fri, Nov 20, 2009 at 12:16 PM, Thomas Heute <<a href="mailto:theute@gmail.com">theute@gmail.com</a>> wrote:<br>
> On 11/19/2009 07:56 PM, Arnaud HERITIER wrote:<br>
>> Thomas I don't know if we have a documentation about our release<br>
>> process to integrate my changes ?<br>
>><br>
> No not yet.<br>
><br>
><br>
>> For Exo-jcr I 'll update our documentation our wiki as soon as i'l<br>
>> have updated your parent.<br>
>><br>
>> On Thursday, November 19, 2009, Thomas Heute<<a href="mailto:theute@gmail.com">theute@gmail.com</a>> wrote:<br>
>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> thanks !<br>
>>><br>
>>> On 11/19/2009 06:25 PM, Arnaud HERITIER wrote:<br>
>>> Hi all,<br>
>>><br>
>>><br>
>>> I just released a new Jboss parent pom (5-beta-5) with<br>
>>> following changes :<br>
>>><br>
>>><br>
>>><br>
>>> [JBBUILD-567<<a href="https://jira.jboss.org/jira/browse/JBBUILD-567" target="_blank">https://jira.jboss.org/jira/browse/JBBUILD-567</a>>]<br>
>>> - Add properties in distributionManagement URLs to allow to override<br>
>>> them<br>
>>> [JBBUILD-569<<a href="https://jira.jboss.org/jira/browse/JBBUILD-569" target="_blank">https://jira.jboss.org/jira/browse/JBBUILD-569</a>>]<br>
>>> - jboss-parent POM should include wagon-webdav configuration<br>
>>> [JBBUILD-571<<a href="https://jira.jboss.org/jira/browse/JBBUILD-571" target="_blank">https://jira.jboss.org/jira/browse/JBBUILD-571</a>>]<br>
>>> - Add sonar plugin in pluginManagement<br>
>>> [JBBUILD-572<<a href="https://jira.jboss.org/jira/browse/JBBUILD-572" target="_blank">https://jira.jboss.org/jira/browse/JBBUILD-572</a>>]<br>
>>> - Upgrade maven-checkstyle-plugin 2.3 -> 2.4<br>
>>> [JBBUILD-573<<a href="https://jira.jboss.org/jira/browse/JBBUILD-573" target="_blank">https://jira.jboss.org/jira/browse/JBBUILD-573</a>>]<br>
>>> - Upgrade maven-ear-plugin 2.3.2 -> 2.4<br>
>>> [JBBUILD-574<<a href="https://jira.jboss.org/jira/browse/JBBUILD-574" target="_blank">https://jira.jboss.org/jira/browse/JBBUILD-574</a>>]<br>
>>> - Upgrade maven-javadoc-plugin 2.6 -> 2.6.1<br>
>>> [JBBUILD-575<<a href="https://jira.jboss.org/jira/browse/JBBUILD-575" target="_blank">https://jira.jboss.org/jira/browse/JBBUILD-575</a>>]<br>
>>> - Upgrade maven-plugin-plugin 2.5 -> 2.5.1<br>
>>> [JBBUILD-576<<a href="https://jira.jboss.org/jira/browse/JBBUILD-576" target="_blank">https://jira.jboss.org/jira/browse/JBBUILD-576</a>>]<br>
>>> - Upgrade maven-resources-plugin 2.4 -> 2.4.1<br>
>>> [JBBUILD-577<<a href="https://jira.jboss.org/jira/browse/JBBUILD-577" target="_blank">https://jira.jboss.org/jira/browse/JBBUILD-577</a>>]<br>
>>> - Upgrade maven-source-plugin 2.1 -> 2.1.1<br>
>>> [JBBUILD-578<<a href="https://jira.jboss.org/jira/browse/JBBUILD-578" target="_blank">https://jira.jboss.org/jira/browse/JBBUILD-578</a>>]<br>
>>> - Upgrade findbugs-maven-plugin 2.1 -> 2.2<br>
>>><br>
>>><br>
>>><br>
>>> What it will change for us ?<br>
>>><br>
>>><br>
>>> 1) Before to deploy snapshots on jboss repo (using webdav),<br>
>>> 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>)<br>
>>> we had to put those settings to not generate invalid checksums :<br>
>>><br>
>>><br>
>>><br>
>>> <server><br>
>>> <id>jboss-snapshots</id><br>
>>> <username>AAAAAA</username><br>
>>> <password>BBBBBB</password><br>
>>> <configuration><br>
>>> <httpConfiguration><br>
>>> <put><br>
>>> <params><br>
>>> <param><br>
>>><br>
>>> <name>http.authentication.preemptive</name><br>
>>> <value>%b,true</value><br>
>>> </param><br>
>>> </params><br>
>>> </put><br>
>>> </httpConfiguration><br>
>>> </configuration><br>
>>> </server><br>
>>><br>
>>><br>
>>> Now it is no more necessary. You have to remove it.<br>
>>><br>
>>><br>
>>> 2) We introduced a property to setup where are deployed<br>
>>> releases (and snapshots).<br>
>>> By default when we release a project Maven is setup with the<br>
>>> parent pom to directly publish to the JBoss SVN repository. The problem<br>
>>> is that it is slow and thus for big projects it can fails because the<br>
>>> upload is too long.<br>
>>> For big projects (or always if you prefer) you can come back<br>
>>> to the old solution which is to have a local checkout of the jboss<br>
>>> repository.<br>
>>> You just launch the perform part of the release with the<br>
>>> additional property jboss.releases.repo.url<br>
>>><br>
>>> mvn release:perform -Djboss.releases.repo.url=file://THE_PATH_OF_YOUR_LOCAL_CHECKOUT<br>
>>> (do not forget the file:// protocol before the path of your<br>
>>> repo, it's an url)<br>
>>> And you commit changes in your local repo.<br>
>>> It has also the advantage to be an atomic commit if your<br>
>>> release fails.<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> I'll update the gatein parent to use it in few minutes. If you<br>
>>> are agree I propose to release the gatein-parent and to update all<br>
>>> gatein projects to use it ?<br>
>>><br>
>>><br>
>>> I'll see also with --<br>
>>> You received this message because you are subscribed to the Google<br>
>>> Groups "JBoss / eXo" group.<br>
>>> To post to this group, send email to <a href="mailto:jbossexo@googlegroups.com">jbossexo@googlegroups.com</a><javascript:_e({}, 'cvml', '<a href="mailto:jbossexo@googlegroups.com">jbossexo@googlegroups.com</a>');>.<br>
>>> For more options, visit this group at<br>
>>> <a href="http://groups.google.com/group/jbossexo?hl=" target="_blank">http://groups.google.com/group/jbossexo?hl=</a>.<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>><br>
>>> You received this message because you are subscribed to the Google Groups "JBoss / eXo" group.<br>
>>> To post to this group, send email to <a href="mailto:jbossexo@googlegroups.com">jbossexo@googlegroups.com</a><javascript:_e({}, 'cvml', '<a href="mailto:jbossexo@googlegroups.com">jbossexo@googlegroups.com</a>');>.<br>
>>> For more options, visit this group at <a href="http://groups.google.com/group/jbossexo?hl=" target="_blank">http://groups.google.com/group/jbossexo?hl=</a>.<br>
>>><br>
>>><br>
>><br>
><br>
> --<br>
><br>
> You received this message because you are subscribed to the Google Groups "JBoss / eXo" group.<br>
> To post to this group, send email to <a href="mailto:jbossexo@googlegroups.com">jbossexo@googlegroups.com</a>.<br>
> To unsubscribe from this group, send email to <a href="mailto:jbossexo%2Bunsubscribe@googlegroups.com">jbossexo+unsubscribe@googlegroups.com</a>.<br>
> For more options, visit this group at <a href="http://groups.google.com/group/jbossexo?hl=" target="_blank">http://groups.google.com/group/jbossexo?hl=</a>.<br>
><br>
><br>
><br>
<br>
--<br>
<br>
You received this message because you are subscribed to the Google Groups "JBoss / eXo" group.<br>
To post to this group, send email to <a href="mailto:jbossexo@googlegroups.com">jbossexo@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href="mailto:jbossexo%2Bunsubscribe@googlegroups.com">jbossexo+unsubscribe@googlegroups.com</a>.<br>
For more options, visit this group at <a href="http://groups.google.com/group/jbossexo?hl=" target="_blank">http://groups.google.com/group/jbossexo?hl=</a>.<br>
<br>
<br>
</div></div></blockquote></div><br></div>