The basic functionality has been implemented in the package fi.helsinki.cs.tmc.client.core.testrunner, in the form of MavenTestrunnerTask and TestrunnerTaskListener of which the TestrunnerListener is generic enough to work with (hopefully) any languages and testrunner tasks.
The task requires the actual client to implement and provide a MavenRunner that knows how to run a single maven goal.
This is because we cannot make any global asumptions about the client's abilities or the users system. For example, the Eclipse IDE has no actual Maven executable and running of any Maven goals has to be done using the integrated Maven of Eclipse IDE.
The other option would be to require the end user to install Maven, which is not something we are prepared to do at this time, since most IDEs already have an integrated way of running Maven.
The basic functionality has been implemented in the package
fi.helsinki.cs.tmc.client.core.testrunner, in the form ofMavenTestrunnerTaskandTestrunnerTaskListenerof which theTestrunnerListeneris generic enough to work with (hopefully) any languages and testrunner tasks.The task requires the actual client to implement and provide a
MavenRunnerthat knows how to run a single maven goal.This is because we cannot make any global asumptions about the client's abilities or the users system. For example, the Eclipse IDE has no actual Maven executable and running of any Maven goals has to be done using the integrated Maven of Eclipse IDE.
The other option would be to require the end user to install Maven, which is not something we are prepared to do at this time, since most IDEs already have an integrated way of running Maven.