[
https://issues.apache.org/jira/browse/HADOOP-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648195#action_12648195
]
Doug Cutting commented on HADOOP-4297:
--------------------------------------
Should we worry about assertions with inadvertent side-effects? If they do,
there's the chance that tests will succeed with assertions enabled and fail
when they're disabled. Perhaps the final release build instructions should
disable assertions? Or am I being too paranoid?
> Enable Java assertions when running tests
> -----------------------------------------
>
> Key: HADOOP-4297
> URL: https://issues.apache.org/jira/browse/HADOOP-4297
> Project: Hadoop Core
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.19.0, 0.20.0
> Reporter: Yoram Kulbak
> Fix For: 0.20.0
>
> Attachments: HADOOP-4297.patch, HADOOP-4297.patch
>
>
> A suggestion to enable Java assertions in the project's build xml when
> running tests. I think this would improve the build quality.
> To enable assertions add the following snippets to the JUnit tasks in
> build.xml:
> <assertions>
> <enable />
> </assertions>
> --
> For example:
> <junit ... >
> ...
> <assertions>
> <enable />
> </assertions>
> </junit>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
