Huân,
You can just remove the test string that's causing the failure for now, i.e.,
remove "Thu, 01 Jan 1970 00:00:00 GMT" from line 88.
As André pointed out (thank-you André) this is due to an existing issue. As far
as I know, there's no production code that actually internally consumes dates
I've added the print, I've got this :
Running org.fcrepo.server.utilities.TestDateUtility
parsing: 1970-01-01T00:00:00.000Z
parsing: 1970-01-01T00:00:00.00Z
parsing: 1970-01-01T00:00:00.0Z
parsing: 1970-01-01T00:00:00Z
parsing: 1970-01-01Z
parsing: 1970-01-01T00:00:00.000
parsing: 1970-01-01T00:00
Thanks Edwin. I am comfortable with checking out and building. I am planning to
do so on WSL 10.0 with Fedora 3.4. If successful, I will try backporting for
WSL 9.2. In the meantime, if you could post the changes required to make Fedora
3.3/3.4 work on WSL 10.x, it will be great.
To answer why
Edwin,
I think this issue is related to
http://www.fedora-commons.org/jira/browse/FCREPO-667.
Best regards,
André
---
Fachinformationszentrum Karlsruhe, Gesellschaft für wissenschaftlich-technische
Information mbH.
Sitz der Gesellschaft:
Huân,
Could you insert a print statement at line 90 to see which date string is
causing the problem? e.g.:
for (String element : dates) {
+System.out.println("parsing: " + element);
assertEquals(EPOCH, DateUtility.parseDateAsUTC(element));
}
And re-ru
Hello developpers
Im trying to build fedora (trunk) from sources, but I get this :
Results :
Failed tests:
testParseDate(org.fcrepo.server.utilities.TestDateUtility)
Tests run: 314, Failures: 1, Errors: 0, Skipped: 0
[INFO]
---
