error upgrading to grails 1.1.1
-
dima767 (at gmail)
- State changed from new to resolved
-
samar
can u tell me what changes did u do to fix this error. and also action do i need to take from my end to fix this error??
-
dima767 (at gmail)
I don't remember exactly, but it has something to do with Hibernate lazy collection proxies being accessed outside of a Session, etc. The fetch type of 'eager' has been set for 'messages' collection in 'Mailbox' model, etc. You could see the exact diffs by going to GitHub (it shows you diffs visually quite nicely).
On your end, you don't have to do anything other then fetching a fresh copy of the source code from GitHub, doing 'grails upgrade', installing necessary plugins and that's it.
-
samar
great work dima, I guess i want to part of grails-crowd development. Can i can contribute to this project and make this a very robust and enterprise application like linked-in
-
dima767 (at gmail)
Sure. Feel free to clone (fork) the GitHub repo and hack away. When you have some features ready, just send me a 'pull' request, so I could incorporate the code into my repo's 'master' branch, etc. That's the beauty of git and GitHub! :-)
If you are not familiar with 'git way of working', GitHub has some nice pointers:
BTW, I just started using new GitHub's 'issues' instead of Lighthouse:
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.