You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jesse McConnell (JIRA)" <ji...@codehaus.org> on 2006/03/14 16:18:29 UTC

[jira] Created: (MANTLR-5) added source scanning so grammar configuration no longer required

added source scanning so grammar configuration no longer required
-----------------------------------------------------------------

         Key: MANTLR-5
         URL: http://jira.codehaus.org/browse/MANTLR-5
     Project: Maven 2.x Antlr Plugin
        Type: Improvement

    Reporter: Jesse McConnell
 Attachments: antlr.patch


I was testing the NoSecurityManager mechanism of getting around system.exit() in the antlr tool's main method and noticed that this plugin had to have the grammar specified in the configuration

so I wired in the stale source scanner from my other plugins

works like a charm, you can either specify the grammar or you can rely on the stale source scanner to find them

like before, will not reexecute antlr if the source grammar hasn't changed.



-- 
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


[jira] Commented: (MANTLR-5) added source scanning so grammar configuration no longer required

Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MANTLR-5?page=comments#action_74939 ] 
            
Vincent Siveton commented on MANTLR-5:
--------------------------------------

Applied the adding resources feature. Thanks.

> added source scanning so grammar configuration no longer required
> -----------------------------------------------------------------
>
>                 Key: MANTLR-5
>                 URL: http://jira.codehaus.org/browse/MANTLR-5
>             Project: Maven 2.x Antlr Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.0-beta-1
>            Reporter: Jesse McConnell
>         Attachments: antlr.patch
>
>
> I was testing the NoSecurityManager mechanism of getting around system.exit() in the antlr tool's main method and noticed that this plugin had to have the grammar specified in the configuration
> so I wired in the stale source scanner from my other plugins
> works like a charm, you can either specify the grammar or you can rely on the stale source scanner to find them
> like before, will not reexecute antlr if the source grammar hasn't changed.

-- 
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

        

[jira] Closed: (MANTLR-5) added source scanning so grammar configuration no longer required

Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MANTLR-5?page=all ]

Vincent Siveton closed MANTLR-5.
--------------------------------

      Assignee: Vincent Siveton
    Resolution: Won't Fix

Grammar configuration is required to define an "order" in the antlr calls (MANTLR-3)

> added source scanning so grammar configuration no longer required
> -----------------------------------------------------------------
>
>                 Key: MANTLR-5
>                 URL: http://jira.codehaus.org/browse/MANTLR-5
>             Project: Maven 2.x Antlr Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.0-beta-1
>            Reporter: Jesse McConnell
>         Assigned To: Vincent Siveton
>         Attachments: antlr.patch
>
>
> I was testing the NoSecurityManager mechanism of getting around system.exit() in the antlr tool's main method and noticed that this plugin had to have the grammar specified in the configuration
> so I wired in the stale source scanner from my other plugins
> works like a charm, you can either specify the grammar or you can rely on the stale source scanner to find them
> like before, will not reexecute antlr if the source grammar hasn't changed.

-- 
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

        

[jira] Updated: (MANTLR-5) added source scanning so grammar configuration no longer required

Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MANTLR-5?page=all ]

Vincent Siveton updated MANTLR-5:
---------------------------------

          Description: 
I was testing the NoSecurityManager mechanism of getting around system.exit() in the antlr tool's main method and noticed that this plugin had to have the grammar specified in the configuration

so I wired in the stale source scanner from my other plugins

works like a charm, you can either specify the grammar or you can rely on the stale source scanner to find them

like before, will not reexecute antlr if the source grammar hasn't changed.



  was:

I was testing the NoSecurityManager mechanism of getting around system.exit() in the antlr tool's main method and noticed that this plugin had to have the grammar specified in the configuration

so I wired in the stale source scanner from my other plugins

works like a charm, you can either specify the grammar or you can rely on the stale source scanner to find them

like before, will not reexecute antlr if the source grammar hasn't changed.



    Affects Version/s: 2.0-beta-1

> added source scanning so grammar configuration no longer required
> -----------------------------------------------------------------
>
>                 Key: MANTLR-5
>                 URL: http://jira.codehaus.org/browse/MANTLR-5
>             Project: Maven 2.x Antlr Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.0-beta-1
>            Reporter: Jesse McConnell
>         Attachments: antlr.patch
>
>
> I was testing the NoSecurityManager mechanism of getting around system.exit() in the antlr tool's main method and noticed that this plugin had to have the grammar specified in the configuration
> so I wired in the stale source scanner from my other plugins
> works like a charm, you can either specify the grammar or you can rely on the stale source scanner to find them
> like before, will not reexecute antlr if the source grammar hasn't changed.

-- 
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