| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0002-Ensure-for-task-is-specified-correctly.patch | Ensure 'for' task is specified correctly. | Michael Gilbert <michael.s.gilbert (at) gmail.com> | no | 2011-09-25 | ||
| 0003-ivy-compatibility.patch | Fixes the compatibility with the version of Ivy in Debian | Daniel Leidert (dale) <daniel.leidert@wgdd.de> | no | |||
| 0004-optional-maven-dependencies.patch | Mark the Maven dependencies as optional to match the package dependencies and the POM deployed on Maven Central | Emmanuel Bourg <ebourg@apache.org> | no | |||
| 0005-outofdate-test.patch | address intermittent test failures Update "outofdate" test case to ensure that the simulated build artifacts (outofdate/gen/*) have dates strictly later than the source files. . It appears that the tests were failure due to a race where "file.done" was considered out of date and thus appeared in the source set, despite being configured as up to date in the test case. . That said, it's not clear to me how it ever worked in the first place given the logic in OutOfData.outOfDate(): . if ((!ret) && (sourceFile != null)) { ret = sourceFile.lastModified() > targetFile.lastModified(); } . My assumption is that the test was previously broken/flaky, but that time was chunkier (larger quanta) until recently and so the source files had the same timestamp and so weren't strictly newer. . This patch also adds the fork=true attribute to the junit task, which resolves spurious test failures observed after the OutOfDate test was patched. |
tony mancill <tmancill@debian.org> | no | debian | vendor | 2018-09-03 |
| 0006-disable-verifydesign-tests.patch | Disables the broken verifydesign tests (already disabled in the Maven POM) | Emmanuel Bourg <ebourg@apache.org> | not-needed |