Hello,<br><br>   Last commit broke the build. And will probably block the night team in VN :-)<br><br><a href="http://builder.exoplatform.org/hudson/view/All/job/gatein-portal-trunk/97/console">http://builder.exoplatform.org/hudson/view/All/job/gatein-portal-trunk/97/console</a><br>

<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: &#39;Times New Roman&#39;; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span class="Apple-style-span" style="border-collapse: collapse; font-family: Verdana,Helvetica,&#39;sans serif&#39;; font-size: 11px;"><pre style="white-space: pre-wrap;">

/home/hudson/hudson/jobs/gatein-portal-trunk/workspace/gatein/portal/trunk/component/pc/src/main/java/org/exoplatform/portal/pc/ExoKernelIntegration.java:[133,61] cannot find symbol<br>symbol  : variable LOCAL_PORTLET_INVOKER_ID<br>

location: interface org.gatein.pc.api.PortletInvoker<br></pre></span></span><br class="Apple-interchange-newline"><b>Questions:</b><br>   How should we behave in such case ?<br>   Can we rollback the commit if the responsible is not present for few hours ? Or let it be and update to the last known stable state.<br>

<br><b>Experimentation:</b><br>   I&#39;ll send the build notifications (only failures and back to normal state) to the gatein-dev list. Tell me if that&#39;s not acceptable also.<br>   Is there another target ML for that ?<br>

<br>The notification rules:<br><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: &#39;Times New Roman&#39;; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><span class="Apple-style-span" style="font-family: Verdana,Helvetica,&#39;sans serif&#39;; font-size: 11px;"><ol>

<li>Every failed build triggers a new e-mail.</li><li>A successful build after a failed (or unstable) build triggers a new e-mail, indicating that a crisis is over.</li><li>An unstable build after a successful build triggers a new e-mail, indicating that there&#39;s a regression.</li>

<li>Unless configured, every unstable build triggers a new e-mail, indicating that regression is still there.</li></ol></span></span><br><br clear="all">Dimitri BAELI - eXo Platform SAS<br>