In order to get a working build of the Core ITs there are a number of steps that needs to be taken. These include checking out the source for the ITs and the version of Maven you want to test. Then there are an elaborate setup of M2_HOME local.repo and some other stuff. There is a shell script to help with this, but it is for Linux/Unix only. If you take a look at the Jenkins jobs that runs the ITs there are several platform dependent steps.
To get more people to help run the ITs in different environments, we need to make this simpler, especially for Windows. So I suggest that we put together an Ant script that can be used by all users, including CI builds, to do the necessary setup. As for releaseability I think that we should have both the windows and osx jobs pass. That being said, it seems that the osx installation is dead and won't be coming back any time soon, so until then we can't rely on it. We have lots of devs running osx so it shouldn't be a problem getting confirmation that the ITs pass on that platform. Since I'm on Windows myself I'm keen to get the Windows job into a runnable state. I did some work on it before, but finally gave up because of the platform dependent steps that was needed, in combination with some limitations in the properties that are available to Jenkins on Windows. I'm willing to work on it again though. Related to this, what's the status on Core ITs for Maven 2? Are the ITs that this thread talk about applicable to Maven 2, or does it use a different set of ITs? On Tue, Aug 20, 2013 at 5:17 PM, Jason van Zyl <[email protected]> wrote: > What do you mean exactly? > > Also what about the releasability question? > > On Aug 20, 2013, at 7:45 AM, Dennis Lundberg <[email protected]> wrote: > > > Thanks for looking into this Jason. > > > > As someone who has tried to fix these builds, I think what we need is a > > platform independent way to set up and run the core ITs. The best choice > is > > probably to use Ant. > > Den 20 aug 2013 16:18 skrev "Jason van Zyl" <[email protected]>: > > > >> I have separated them like the following to delineate the stable builds > >> that are a reliable measure of the ITs working and things that have > either > >> been failing for months, or things we can't reasonably maintain. > >> > >> If these are working I consider Maven releasable: > >> > >> https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/ > >> > >> I put the rest of them here: > >> > >> > https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs%20(unstable)/ > >> > >> If the jobs in the first group are passing can we consider that being > in a > >> reasonable state for a release? > >> > >> Thanks, > >> > >> Jason > >> > >> ---------------------------------------------------------- > >> Jason van Zyl > >> Founder, Apache Maven > >> http://twitter.com/jvanzyl > >> --------------------------------------------------------- > >> > >> > >> > >> > >> > >> > >> > >> > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > We know what we are, but know not what we may be. > > -- Shakespeare > > -- > Dennis Lundberg
