[ http://jira.codehaus.org/browse/SUREFIRE-35?page=comments#action_63629 ]
Brett Porter commented on SUREFIRE-35: -------------------------------------- we also need to watch out for executing this code on jdk 1.3 > refine use of assertion enablement > ---------------------------------- > > Key: SUREFIRE-35 > URL: http://jira.codehaus.org/browse/SUREFIRE-35 > Project: surefire > Type: Improvement > Versions: 2.0 > Reporter: Brett Porter > Assignee: Jason van Zyl > > > Currently, the assertions are correctly enabled on the classloader when not > forking. However, when forking, setting them on the classloader didn't work, > so -ea is passed in to the forked process. > This is not harmful, though if there were assertions in the surefire provider > or its dependencies (eg, testng), they would be checked unnecessarily. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
