<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Local build on LiveReload component using 'mvn clean verify -Dtpc.version=4.30.5.Alpha5-SNAPSHOT' works fine, but I get <div><pre>HTTP Server 'Gateway Timeout': <a href="http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.kepler/content.xml">http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.kepler/content.xml</a></pre><div>on Jenkins: <a href="https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_4.1.kepler/job/jbosstools-livereload_41/26/console">https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_4.1.kepler/job/jbosstools-livereload_41/26/console</a></div><div><br></div><div><div apple-content-edited="true">
/Xavier<br><br><br>
</div>
<br><div><div>On May 22, 2013, at 6:08 PM, Max Rydahl Andersen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>we probably should remove our relativePath references to avoid this problem.<br><br>/max<br><br>On Wed, May 22, 2013 at 03:11:00PM +0200, Mickael Istria wrote:<br><blockquote type="cite">On 05/22/2013 02:58 PM, André Dietisheim wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">did you "git pull" in your jbosstools-build folder?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I can build using the Alpha5 TP once I update jbosstools-build <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(parent pom in openshift is referenced via <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><relativePath>../jbosstools-build/parent/pom.xml</relativePath><br></blockquote></blockquote><blockquote type="cite">On a side note, I highly recommend you to not have a jbosstools-build <br></blockquote><blockquote type="cite">folder (for example rename it to jbosstools--build - with 2 dashes). <br></blockquote><blockquote type="cite">That way, you're sure you build will consume what's available on Nexus <br></blockquote><blockquote type="cite">or what has been "mvn install"ed rather than the stuff it finds in the <br></blockquote><blockquote type="cite"><relativePath/> for parent, and the behavior you'll get will be closer <br></blockquote><blockquote type="cite">from what will happen on Jenkins.<br></blockquote><blockquote type="cite">Since we now push all that stuff to Nexus, you can even delete your <br></blockquote><blockquote type="cite">local clone of jbosstools-build.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Cheers,<br></blockquote><blockquote type="cite">-- <br></blockquote><blockquote type="cite">Mickael Istria<br></blockquote><blockquote type="cite">Eclipse developer at JBoss, by Red Hat <<a href="http://www.jboss.org/tools">http://www.jboss.org/tools</a>><br></blockquote><blockquote type="cite">My blog <<a href="http://mickaelistria.wordpress.com">http://mickaelistria.wordpress.com</a>> - My Tweets <br></blockquote><blockquote type="cite"><<a href="http://twitter.com/mickaelistria">http://twitter.com/mickaelistria</a>><br></blockquote><br><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">jbosstools-dev mailing list<br></blockquote><blockquote type="cite"><a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br></blockquote><blockquote type="cite"><a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br></blockquote><br>_______________________________________________<br>jbosstools-dev mailing list<br><a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/jbosstools-dev<br></div></blockquote></div><br></div></div></body></html>