Re: [vote] Move the maven-antlr-plugin to the mojo project
On Sat, Jul 14, 2007 at 11:33:00AM -0400, Vincent Siveton wrote: > A release could be done shortly but I would like to move the > maven-antlr-plugin and maven-antlr3-plugin (in sandbox) to Mojo > project. > > During the last year, I am the main committer on this project. > Recently, David Holroyd provided a new plugin that supports Antlr v3, > and submitted some patches. Unfornately, he is not an ASF committer. > I could take care of David's patches but I think it should be good to > give a new life of this project in the Mojo land. It would be more > easy to give access to David, so he could maintain it as he wants. I would just like to thank Vincent for all the help he's given me with this, and to say that it would be great to be able to regain the possibility of directly making changes (and releases) myself :) ta, dave -- http://david.holroyd.me.uk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Antlr2/3 compatibility with maven-antlr3-plugin
On Fri, Jul 13, 2007 at 06:21:24AM +1000, Brett Porter wrote: > I also didn't think stringtemplate used antlr2 at runtime, I thought > it was just at compile time? The StringTemplate build needs the ANTLRv2 tool to compile its grammar and the StringTemplate artifact needs the ANTLRv2 'runtime' to execute the resulting parser. In v2, tool and runtime are in the same artifact, so the dependency is correct, I think. ta, dave -- http://david.holroyd.me.uk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Antlr2/3 compatibility with maven-antlr3-plugin
Hi, On Thu, Jul 12, 2007 at 12:08:53PM +0200, Jochen Kuhnle wrote: > I tried out the antlr3 plugin and ran into a dependency problem: > antlr-3.0 depends on stringtemplate-3.0 which depends on antlr-2.7.x. > Since antlr-2 and -3 are fundamentally incompatible (API packages > renamed, grammar file format changed), this does not work. However, the two ANTLRs have different groupIds, so there should be no problem due to these dependencies, I think? antlr:antlr:2.7.x vs. org.antlr:antlr:3.0 (Still pretty confusing though.) What specific errors did you encounter? > I propose to change the artifactId of antlr-3.0 to antlr3-3.0, and to > change the default directories of the plugin to "src/main/antlr3" and > "target/generated-sources/antlr3". This allows using antlr-2.x and > antlr-3.0 and the respective plugins side by side. I took "src/main/antlr" as the default for the v3 plugin on the assumption that if anyone wanted to do this, they could just specify different folders by hand. Also, IIRC, the v2 plugin does not have a default directory for the v3 plugin to clash with -- you have to explicitly tell it where to find the source v2 grammars, I think? I think that most people will just be using one version of the plugin, and the few wanting both can configure a non-default value. If you can show a reasonable case for changing the default, I'll take a look though. ta, dave -- http://david.holroyd.me.uk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-antlr3-plugin
Hi there, I am the author of the maven-antlr3-plugin, which Vincent Siveton kindly added to the Maven sandbox recently: http://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-antlr3-plugin/ I would like to update the documentation a bit and do a release from the newly Apache-branded codebase, but I'm not an Apache committer. How can I get these things to happen? Must I submit patches via JIRA and ask someone here to release for me, or should I pursue developer access for myself? thanks! dave -- http://david.holroyd.me.uk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
