Hi,
To be completely fair, I think that the problem was the size of the
project. We managed to solve most of the problems we faced with little
or no effort. But then we found like 200 tests (of a base of more
5000) were not fixed. These tests didn't look easy to fix, and we
decide to postpone the upgrade as we had some work to deliver.
I also took a look to the possibility to migrate to 2.4.5 and looks
like our code, have some problems we need to solve before that (for
instance we use static Holders), as was migrated from a previous
grails version to 2.3.
To be honest I think that migrating from 2.3.x to 2.5.x in an average
project (I think mine is big with over 200k lines of code reported by
grails stats) could be done without too much pain. But I'm not sure of
be able to say the same thing about grails 3.x.x.
Regards
Esau Rodriguez.
> --
> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
grails-dev-disc...@googlegroups.com.
> To post to this group, send email to
grails-de...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/grails-dev-discuss/0B025FE8-C4D5-4371-9E0D-0E9443D5B347%40ociweb.com.
> For more options, visit
https://groups.google.com/d/optout.
--
Esaú Rodríguez
esa...@gmail.com