Good points I think. I'd like to see a quicker build, but having those tests as part of the main build is useful.
Maybe we can exclude them with a profile and publish the Maven command to build without them? Might be a simple solution to get the best of both worlds? Jon > On 29 Mar 2014, at 08:55, Andy <[email protected]> wrote: > > I agree with Romain that the example tests are an important way of judging if > the build is stable. In the past I have always based internal releases on > them all passing. > > If we moved them then I'd still like to see them on the buildbot. > > We could also just leave them in trunk and mirror just the examples so that > we can merge changes back. > >> On 29.03.2014 09:37, Romain Manni-Bucau wrote: >> -100 excepted if for *each* example you move tests to main build too. >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2014-03-29 9:35 GMT+01:00 Jean-Louis MONTEIRO <[email protected]>: >>> +1 >>> Le 29 mars 2014 06:01, "Thiago Veronezi" <[email protected]> a écrit : >>> >>>> +1 >>>> Was chatting with Gerhard at JavaLand and he mentioned moving examples to >>>> its own section of the repository. >>>> >>>> In our github mirror, we actually have quite a few people looking (110 >>>> forks, 34 stars) >>>> >>>> - https://github.com/apache/tomee >>>> >>>> If we move the examples out to their own "repo" and mirrored it on Github, >>>> we might get a lot more contributions. >>>> >>>> >>>> Thoughts? >>>> >>>> >>>> -David > > > -- > Andy Gumbrecht > Tomitribe Corporation > http://www.tomitribe.com >
