<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">We're talking a new repo for integration stack bot tests - to separate it from the jbt core bot tests in jbosstools-integration-tests. So, yes, this new repo would be jbosstools integration stack integration tests :) But probably called something simpler, e.g. jbosstools-integration-stack-tests as suggested.<div><br></div><div>-Martin<br><div><br><div><div>On 31. 1. 2013, at 21:35, Nick Boldt <<a href="mailto:nboldt@redhat.com">nboldt@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">A new repository for bot tests?<br><br>Why not <a href="https://github.com/jbosstools/jbosstools-integration-tests/">https://github.com/jbosstools/jbosstools-integration-tests/</a> ?<br><br>On 01/31/2013 12:31 PM, Max Rydahl Andersen wrote:<br><blockquote type="cite"><blockquote type="cite"><br>what do you think about having new git repository for SOA related bot tests?<br></blockquote><br>We should be using integration-stack now instead of just SOA :)<br><br><blockquote type="cite">SOA tests include bpel, jbpm, modeshape, teiid designer etc. And these components are independently released.<br>Now, the soa tests are in jbosstools-integration-tests together with jbt core tests.<br><br>The problem is that the next soa release will be for juno, so I'm developing tests under Juno.<br></blockquote><br><blockquote type="cite">It means committing to jbosstools-4.0.x branch while people for JBT core commit to the master branch (Kepler).<br>But what happens when I start developing soa tests for Kepler? Possibly commit my juno changes to kepler branch.<br></blockquote><br>Yes, you merge them down.<br><br><blockquote type="cite">What happens when there is another eclipse release? It seams that I will be still behind the master branch :(<br></blockquote><br>That is/will hopefully change.<br><br><blockquote type="cite">Another reason is that soa tests have nothing in common with core tests. Everyone is still dividing the tools into core and soa.<br></blockquote><br><blockquote type="cite">So, lets start discussing about pros and cons ;-)<br></blockquote><br>Well, technically it is fine/ok for this but I can see the advantage of creating a jbosstools-integration-stack-test repo (or similar named) as<br>these tests would be related to jbosstools-integration-stack releases.<br><br>It also maps to the notion of having coretests and integrationstacktests updatesites for dev/build testing.<br><br>So I'm +1 on doing a split - but still need to solve the reddeer/botext scenario and you would still have similar job of working in different branches in this stack<br>since both 4.0.x and 4.1 stuff will be active.<br><br>/max<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><br></blockquote><br>-- <br>Nick Boldt :: JBoss by Red Hat<br>Productization Lead :: JBoss Tools & Dev Studio<br><a href="http://nick.divbyzero.com">http://nick.divbyzero.com</a><br><br><br>_______________________________________________<br>jbosstools-dev mailing list<br>jbosstools-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/jbosstools-dev<br></blockquote></div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div apple-content-edited="true"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 12px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; 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; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>--</div><div>Martin Malina<br>JBoss QA Engineer<br>Red Hat Czech s.r.o.<br>Purkynova 99<br>612 45 Brno, Czech Republic<br></div><div><br></div><div><span class="Apple-style-span" style="font-size: medium; ">Tel.: +420 532 294 265</span></div><div><span class="Apple-style-span" style="font-size: medium; "><br></span></div></div></span></div></div></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br></div></div></body></html>