Summary: | <junitreport> broken on JDK 7 when a SecurityManager is set | ||
---|---|---|---|
Product: | Ant | Reporter: | Jesse Glick <jglick> |
Component: | Optional Tasks | Assignee: | Ant Notifications List <notifications> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | jglick, markuskeller |
Priority: | P2 | ||
Version: | 1.8.2 | ||
Target Milestone: | 1.8.3 | ||
Hardware: | PC | ||
OS: | Linux | ||
Bug Depends on: | 52382 | ||
Bug Blocks: |
Description
Jesse Glick
2011-08-16 22:06:37 UTC
Unfortunately just calling tfactory.setFeature("http://javax.xml.XMLConstants/feature/secure-processing", false) in TraXLiaison.getFactory does not work: javax.xml.transform.TransformerConfigurationException: FEATURE_SECURE_PROCESSING: Cannot set the feature to false when security manager is present. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.setFeature(TransformerFactoryImpl.java:417) Only workaround seems to be to use reflection to override the state of _isNotSecureProcessing. Fixed: revision 1158470 (In reply to comment #3) > Fixed: revision 1158470 This fix has NOT been shipped with Ant 1.8.3 nor 1.8.4, see e.g. http://archive.apache.org/dist/ant/source/apache-ant-1.8.3-src.tar.gz This bug is supposed to fix https://bugs.eclipse.org/bugs/show_bug.cgi?id=384757 The fix is indeed in 1.8.3; you need to see http://svn.apache.org/viewvc?view=revision&revision=1222724 from bug #52382 for the revised patch (since the change to AggregateTransformer.java was reverted). Whether this patch is "supposed" to fix the Eclipse bug you quote, or indeed if that bug is even related, is a question which I do not know the answer to; if you continue to have problems in Eclipse using 1.8.3+ then probably you should file a separate bug report after doing some investigation to confirm that the problem lies in Ant code. OK, thanks for the infos and sorry for interrupting. It looks like this workaround is not enough to fix the bug we're seeing in Eclipse. I'll follow up there and see if there's abetter fix for the root cause in the Oracle JDK when a SecurityManager is present. (In reply to comment #6) > not enough to fix the bug we're seeing in Eclipse bug #54641 It looks as if the bug was back with JDK9-ea128, looking into it. (In reply to Stefan Bodewig from comment #8) > It looks as if the bug was back with JDK9-ea128, looking into it. https://bz.apache.org/bugzilla/show_bug.cgi?id=60060 |