poiati/gmongo

Support for Groovy 1.7?

stefankendall opened this issue · 4 comments

Is there any chance you could maintain a 1.7 build in maven for gmongo updates? I'm using grails 1.3.7, so I'm locked into 1.7.10. I'm investigating what it would take to move to Grails 2 right now, but it would be much simpler if there was a 1.7 build.

By moving to 1.8, all 1.3.7 Grails users are locked out. :/

Hello Stefan,

Version 0.9.2 don't fit your needs? If some breaking change occurs in
Groovy 1.7.x I can fix it and release a 0.9.2.1 for example.

Cheers!

[]'s
Paulo Poiati

blog.paulopoiati.com

On Mon, Jan 30, 2012 at 8:20 PM, Stefan Kendall <
reply@reply.github.com

wrote:

Is there any chance you could maintain a 1.7 build in maven for gmongo
updates? I'm using grails 1.3.7, so I'm locked into 1.7.10. I'm
investigating what it would take to move to Grails 2 right now, but it
would be much simpler if there was a 1.7 build.

By moving to 1.8, all 1.3.7 Grails users are locked out. :/


Reply to this email directly or view it on GitHub:
#9

Paulo,

I'm looking more at the mongo-java-driver dependency. I'm not sure any
changes from gmongo are needed, but I'd like to keep up on updates
from both gmongo and the mongo driver.

Have you needed to make any changes to support driver updates during
development?

My workaround plan was to fork 0.9.2 and try to keep the mongo java
driver current, but I didn't think this was a good long term solution.

On Jan 30, 2012, at 6:24 PM, Paulo Gabriel Poiati
reply@reply.github.com
wrote:

Hello Stefan,

Version 0.9.2 don't fit your needs? If some breaking change occurs in
Groovy 1.7.x I can fix it and release a 0.9.2.1 for example.

Cheers!

[]'s
Paulo Poiati

blog.paulopoiati.com

On Mon, Jan 30, 2012 at 8:20 PM, Stefan Kendall <
reply@reply.github.com

wrote:

Is there any chance you could maintain a 1.7 build in maven for gmongo
updates? I'm using grails 1.3.7, so I'm locked into 1.7.10. I'm
investigating what it would take to move to Grails 2 right now, but it
would be much simpler if there was a 1.7 build.

By moving to 1.8, all 1.3.7 Grails users are locked out. :/


Reply to this email directly or view it on GitHub:
#9


Reply to this email directly or view it on GitHub:
#9 (comment)

Just a few, nothing really big. Anyway, if you find any new method in the driver API you want to use and GMongo does not support in the current Groovy 1.7.x branch you open a new issue here ok?

Maintaining a branch is easy enough, I guess. So long as you don't start relying on 1.8 features, the 1.7 branch is easy to keep in parallel. Start using the fun annotations, though, and it'll be a different story. ;)