[
https://issues.apache.org/jira/browse/HADOOP-9051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Lu resolved HADOOP-9051.
-
Resolution: Fixed
Fix Version/s: 1.1.2
1.2.0
Committed trivial patch to branch
Suresh Srinivas created HADOOP-9145:
---
Summary: Remove CRLF endings from files
Key: HADOOP-9145
URL: https://issues.apache.org/jira/browse/HADOOP-9145
Project: Hadoop Common
Issue Type: Bug
Chris Nauroth created HADOOP-9144:
-
Summary: FindBugs reports new warnings in branch-trunk-win
Key: HADOOP-9144
URL: https://issues.apache.org/jira/browse/HADOOP-9144
Project: Hadoop Common
I
One approach we've taken in the past is making the junit test skip
itself when some precondition is not true. Then, we often create a
property which people can use to cause the skipped tests to become a
hard error.
For example, all the tests that rely on libhadoop start with these lines:
> @Test
The swiftfs tests need only to run if there's a target filesystem; copying
the s3/s3n tests, something like
test.fs.swift.name
swift://your-object-store-herel/
How does one actually go about making junit tests optional in mvn-land?
Should the probe/skip logic be in the code -which c
Ivan A. Veselovsky created HADOOP-9143:
--
Summary: repair test
org.apache.hadoop.fs.http.server.TestHttpFSWithKerberos
Key: HADOOP-9143
URL: https://issues.apache.org/jira/browse/HADOOP-9143
Proje
