Grails 2.3.0

[Osian Hedd Hughes]

Hi,

Is there any plan to upgrade the plugin to work with the latest grails release?

I know this can be done by using "ivy" as the dependency resolver, but unfortunately, I need to use the "maven" resolver because we need to use hibernate 4 (and this doesn't seem to work with ivy).

If there are no plans to upgrade the plugin, is it possible for me to do the upgrade and then give you the code to add & create an official release if I'm successful?

Thanks,

Osian

[Predrag Knežević]

> Is there any plan to upgrade the plugin to work with the latest grails
> release?

Sure, but we did not make any patch yet. Your contributions are
welcome, when you are ready, submit a pull request on the Github.

[Osian Hedd Hughes]

Ok, great.

Is there any plans to support 2.2.2 with new features (post 0.9.1)? because the patch work for moving to 2.3.0 will mean that the plugin has to be for version 2.3.x > (due to the maven support, etc.).

I suppose my question is, what should the version number be that I submit? 0.9.2-SNAPSHOT?

Thanks

[David Dawson]

I for one would like to support 2.x for a while.  I only just got one of my clients onto it.

I think the first thing is to have a patch ready and then we can all have a look and decide what to do.

--
 
---
You received this message because you are subscribed to the Google Groups "grails-gwt" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-gwt+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[David Dawson]

As an update on grails 2.3.0 support.

I pushed this new plugin a week or so ago.  http://grails.org/plugin/extended-dependency-manager

This extracts the ivy support that is currently in the GWT plugin and adds aether support to it.

As soon as the GWT plugin is rebased to use this new plugin, it will be compatible with 2.3/ Aether as well as Ivy on previous versions.

I don't have the time to get this done in the next week or so, but if anyone wants to have a go at integrating the GWT plugin with it, that would be fab.  

It'll be a case of removing code from the GWT plugin scripts and replacing it with calls to extended-dependency-manager functions.  Hopefully, that is, it's not been heavily tested.

Otherwise I'll get to it in a fortnight

Best,

David.

On Wednesday, 11 September 2013 07:19:59 UTC+1, David Dawson wrote:

I for one would like to support 2.x for a while.  I only just got one of my clients onto it.

I think the first thing is to have a patch ready and then we can all have a look and decide what to do.

On 11 Sep 2013 05:37, "Osian Hedd Hughes"  wrote:

Ok, great.

Is there any plans to support 2.2.2 with new features (post 0.9.1)? because the patch work for moving to 2.3.0 will mean that the plugin has to be for version 2.3.x > (due to the maven support, etc.).

I suppose my question is, what should the version number be that I submit? 0.9.2-SNAPSHOT?

Thanks

On Tuesday, 10 September 2013 21:43:42 UTC+2, pedjak wrote:

> Is there any plan to upgrade the plugin to work with the latest grails
> release?

  Sure, but we did not make any patch yet. Your contributions are
welcome, when you are ready, submit a pull request on the Github.

--
 
---
You received this message because you are subscribed to the Google Groups "grails-gwt" group.

To unsubscribe from this group and stop receiving emails from it, send an email to grails-gwt+unsubscribe@googlegroups.com.