Well it really depends whether the Antlr plugin is intended to ever
support Antlr 3 or 4. I made the distinction that as of Antlr 2 there
is just a single jar containing both the buildtime and runtime classes.
Starting in 3 they split those up into 2 jars.
So if the plugin is only ever going to target Antlr 2, I think it makes
sense that it "export" the Antlr jar.
And as for Groovy, I may be wrong not being a Groovy developer, but isnt
that considered more of a "provided dependency"? Something the runtime
environment would provide?
On 05/09/2011 01:46 PM, Peter Niederwieser wrote:
Steve Ebersole wrote:
As opposed to the antlr plugin doing that?
I didn't say that. I'm just wondering if there is a reason why none of the
plugins (Antlr, Groovy, ...) do this. If you consider this a bug, please
submit an issue.
--
Peter Niederwieser
Developer, Gradle
http://www.gradle.org
Trainer& Consultant, Gradleware
http://www.gradleware.com
Creator, Spock Framework
http://spockframework.org
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Antlr-dependenciesnot-being-added-to-generated-poms-tp4378307p4382610.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Steve Ebersole <[email protected]>
http://hibernate.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
