| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
of the project
|
| |\
| |
| | |
Replace assert by simpler but equivalent calls.
|
| | | |
|
| |/ |
|
| |
|
|
| |
implementations decide whether to use legacy or new style display names for test identifiers
|
| | |
|
| | |
|
| |
|
|
| |
find . -type f -exec sed -i "s/http:\/\/www.apache.org\/licenses\/LICENSE-2.0/https:\/\/www.apache.org\/licenses\/LICENSE-2.0/" {} \;
|
| |
|
|
|
|
| |
functionality
This closes #93 pull request at github/apache/ant repo
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for each of the test class that are selected by the <testclasses> usage
In 1.10.5 version (the latest released) of Ant, we used to launch
multiple LauncherDiscoveryRequest (a JUnit 5 construct), one each
for a test class, that belonged to the <testclasses> usage. Commit
3f806148c3f3542b8526d5f91f10d6189bf0607d changed it to launch one
single LauncherDiscoveryRequest (and including all those test
classes in that request) because it seemed more logical to do so.
However, recent tests/experimentation of the master branch has
shown that it introduces complexities when the "legacy-xml"
listener (the one which supports generating test results in xml
format that junitreport understands) is used. These complexities
include - expecting each test class to have a separate report file,
but isn't limited to that. Solving these issues isn't easy and
probably not worth it, given that the only reason we started using
a single LauncherDiscoveryRequest is because it just seemed logical
and there is no other strong reason to do so. This commit switches
back to the behaviour that's been there in 1.10.5 version, to issue
multiple separate LauncherDiscoveryRequest(s) one each for the
test class that's selected through the use of <testclasses>.
|
| |
|
|
|
|
|
|
|
| |
junitlauncher
- Allows Ant runtime libraries to be excluded and thus letting the user have control over where those library jars come from
- Allows JUnit platform libraries to be excluded and thus letting the user have control over where those library jars come from
Plus added testcases to verify this feature
|
| | |
|
| |
|
|
| |
just like the vintage engine ones
|
| |
|
|
|
| |
This reverts commit 2f64e0b51c295960cb15aa77c7c1f447b2518e14.
Discussion in ant dev mailing list https://www.mail-archive.com/dev@ant.apache.org/msg47356.html
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@1588563 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@1523198 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@1453094 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@1452675 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@1452674 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@691622 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
caused a timeout or crashed the forked VM. PR 37241.
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@689751 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@637939 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@482069 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@448636 13f79535-47bb-0310-9956-ffa450edef68
|