Seriously contemplating removing multipul runtime versions for gmaven

[Jason Dillon]

... ie. a single plugin version will only support a single version of groovy.  If you want an older version of groovy, use an older version o f gmaven.  May support the last 2 versions as trees.  But its starting to look like having a single plugin supporting both is just causing more problems than its worth...

:-(

--jason


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Jason Smith-11]

+1

I think that is a great idea. It would simplify both usage and maintenance, I think.  I can't think of a decent reason not to do this.

Jason Smith
________________________________________
From: Jason Dillon [[hidden email]] On Behalf Of Jason Dillon [[hidden email]]
Sent: Saturday, December 12, 2009 4:50 AM
To: [hidden email]
Subject: [groovy-dev] Seriously contemplating removing multipul runtime versions for gmaven

... ie. a single plugin version will only support a single version of groovy.  If you want an older version of groovy, use an older version o f gmaven.  May support the last 2 versions as trees.  But its starting to look like having a single plugin supporting both is just causing more problems than its worth...

:-(

--jason


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Peter Niederwieser]

I think this is the right approach. One major version of GMaven per major version of Groovy, ideally released on the same day. Minor releases whenever necessary.
The current model is too difficult to handle, especially if one needs a different (minor) version of Groovy from the one pulled in by GMaven.
If possible, GMaven should not pull in ANY version of Groovy and just use the one defined in the user POM (in the general <dependency> section). Usually this is done with scope "provided", but I'm not sure if it also works in the plugin case.

Cheers,
Peter
 

Jason Dillon wrote

... ie. a single plugin version will only support a single version of groovy.  If you want an older version of groovy, use an older version o f gmaven.  May support the last 2 versions as trees.  But its starting to look like having a single plugin supporting both is just causing more problems than its worth...

:-(

--jason


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email