[ http://jira.codehaus.org/browse/MANTLR-12?page=all ]
Milos Kleint updated MANTLR-12:
-------------------------------
Attachment: ANTLR-12.patch
here's a suggested patch.
the security manager is still set, but when failing to set it, assume the
current manager will be able to cope with System.exit().
had to handle the error messaging differently because sometimes the hints from
the custom SM are not available.
a rather complex solution to the problem would be to execute antlr externally,
like the ant task is doing..
> setting custom security manager might fail in embedded environment
> ------------------------------------------------------------------
>
> Key: MANTLR-12
> URL: http://jira.codehaus.org/browse/MANTLR-12
> Project: Maven 2.x Antlr Plugin
> Issue Type: Bug
> Reporter: Milos Kleint
> Attachments: ANTLR-12.patch
>
>
> when the antlr plugin is run in embedded environment, eg. in netbeans IDE
> integration, it cannot be taken for granted that the setting of new security
> manager will succeed.
> [antlr:generate {execution: default}]
> [INFO]grammar: /space/src/hudson/main/core/src/main/grammar/crontab.g
> [INFO]------------------------------------------------------------------------
> [ERROR]FATAL ERROR
> [INFO]------------------------------------------------------------------------
> [INFO]null
> [INFO]------------------------------------------------------------------------
> [INFO]Trace
> java.lang.SecurityException
> at
> org.netbeans.TopSecurityManager.checkSetSecurityManager(TopSecurityManager.java:351)
> at
> org.netbeans.TopSecurityManager.checkPermission(TopSecurityManager.java:315)
> at java.lang.System.setSecurityManager0(System.java:273)
> at java.lang.System.setSecurityManager(System.java:264)
> at
> org.apache.maven.plugin.antlr.AntlrPlugin.execute(AntlrPlugin.java:99)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:610)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:551)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:530)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:309)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:276)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:393)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182)
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:760)
> at
> org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:257)
> at
> org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:129)
> [INFO]------------------------------------------------------------------------
--
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
