[
https://issues.apache.org/jira/browse/FLUME-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404209#comment-13404209
]
Hari Shreedharan commented on FLUME-1174:
-----------------------------------------
I need your comments on FLUME-1333. A feature to output Flume's version and
hash of the sources would not work on Windows as of now, but Flume will
work(provided someone writes an agent script), so will the build. As such, that
commit does not break anything, it just happens so that one feature available
on *nix will not be available on Windows. You can make that feature available
on Windows, if someone can write a script similar to the
flume-ng-core/scripts/saveVersion.sh.
If you guys are ok with this, please comment on FLUME-1333 so that Ralph will
revert his veto.
> Attempt to build Flume v1.1.0 on Windows 7 x64 fails
> ----------------------------------------------------
>
> Key: FLUME-1174
> URL: https://issues.apache.org/jira/browse/FLUME-1174
> Project: Flume
> Issue Type: Bug
> Affects Versions: v1.1.0
> Environment: Windows 7 - 64 Bit - jdk1.7u4 - mvn 3.0.4
> Reporter: Jeff Lord
> Assignee: Alexander Alten-Lorenz
> Attachments: FLUME-1174.patch,
> org.apache.flume.source.TestExecSource.zip
>
>
> It looks as if the src is expecting to be built on Linux.
> Attempting to build on Windows 7 fails with the below error that references a
> missing /etc/passwd file.
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.156 sec
> Running org.apache.flume.TestCounterGroup
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.109 sec
> Results :
> Failed tests: testRestart(org.apache.flume.source.TestExecSource)
> Tests in error:
> test(org.apache.flume.serialization.TestBodyTextEventSerializer): Unable to
> de
> lete file: src\test\resources\events.txt
> testProcess(org.apache.flume.source.TestExecSource): \etc\passwd (The
> system c
> annot find the path specified)
> Tests run: 114, Failures: 1, Errors: 2, Skipped: 2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
