You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 5, 2020. It is now read-only.
Currently the config uses a patched version of Ant 1.7, to get better reporting of UnitTests.
The dependancy of this patched version of Ant means we can't use the latest version of Ant, which in turn means we also have a dependancy on Ant Contrib for some features that by now are also availlable in Ant itself.
The dependancy on the patched Ant version and the derived dependancy on Ant Contrib means that the process of setting up is more complicated that it has to be: if the config could just use the latest Ant version, Jenkins' Ant plugin could handle the installation of Ant.
In order to get rid of the dependancy on the patched Ant version, an alternative way to get useful UnitTest reporting should be figured out. Possible options (identified thus far):
post process the XML report generated by JUnit to restructure it
Get Servoy to generate the Test Suite(s) differently
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the config uses a patched version of Ant 1.7, to get better reporting of UnitTests.
The dependancy of this patched version of Ant means we can't use the latest version of Ant, which in turn means we also have a dependancy on Ant Contrib for some features that by now are also availlable in Ant itself.
The dependancy on the patched Ant version and the derived dependancy on Ant Contrib means that the process of setting up is more complicated that it has to be: if the config could just use the latest Ant version, Jenkins' Ant plugin could handle the installation of Ant.
In order to get rid of the dependancy on the patched Ant version, an alternative way to get useful UnitTest reporting should be figured out. Possible options (identified thus far):
The text was updated successfully, but these errors were encountered: