Latest version on grails website?

[joshuacoles]

Hello,

I was trying to make a basic chat system for my app and was going to use this plug�in to create it. After attempting draft a system I found that the version of the plugin at http://grails.org/plugin/events-push (1.0.M7) included references to the now removed ConfigurationHolder and also used the resources plugin, which at least on the version that it was using (1.2.RC3) did not work with my version Grails (2.4.0 acording to application.properties).

I then looked at the Github And saw that the issue was fixed (I think) but was not push to the Grails website. Would it be possible for you to pushed an update to the Grails website?

Also here are the log when run from Intellij and a copy of my BuildConfig.groovy. Please tell me if you need any more info and I appoligise if I have have messed this up on my end.

Many thanks Joshua.

[bdbull]

Can I +1 this please?

[msmolyak]

Hello Stephen!

In order to use the latest version of your excellent plugin I had to clone the repo and build it locally changing the version from 1.0.0-BUILD-SNAPSHOT to 1.0.0. Then I had to install it to the local Maven repo, commit the plugin ZIP and POM file into the project repo and supply instructions for team members for adding the plugin to their local Maven repos. Perhaps there is a more straightforward way for sharing the unpublished version of this plugin, but I am not aware of it.

The best solution, of course, would be for you to publish the latest version of this plugin into Grails Central. Is there a reason not to do it? Please let me know if you plan to do it or if I may do it for you.

Thank you,

Michael Smolyak

[atahanozer]

+1

[longwa]

To offer my personal experience, you are WAY better off using the "spring-websocket" plugin if you are able to use Grails 2.4.x. We were in the same situation with events-push and ended up realizing that it's basically a dead project. It's actually quite simple to reactor combined with spring-websocket to do exactly the same thing that events-push is doing. In fact, I think the spring-websocket author has some examples to that end.

I tried and tried to get any comment or reply from @smaldini, but it was wasted effort. Even to just get a confirmation that the project was dead or dying was too much to ask.

On the other hand, @zyro23 is great and very responsive to feedback on his websocket plugin. He's also very plugged into the Grails community and active on the mailing list.

[mpccolorado]

Thanks for telling us your experience @longwa!

I will look to "spring-websocket" plugin! =)

PS: I really liked this plugin but I think the same as you!

[zyro23]

hi, a note regarding grails3: @smaldini is working a lot on reactor which again is the foundation of the new grails3 grails-events plugin, which again is a core plugin from grails3 on (https://github.com/grails/grails-core/tree/master/grails-plugin-events).

reg. the typical events-push use case, just as @longwa said, reactor and spring-websocket make a good team.

[jfarcand]

@zyro23 Guys, don't start me on 'Spring-websocket`. This is the worse case scenario and I recommend every one to not go that route. Just use this Grails plug in instead https://github.com/kensiprell/grails-atmosphere-meteor . Spring-WebSocket will lock you with Spring, contains a lot of issues, etc. Don't use it!

[zyro23]

@jfarcand atmosphere is a great solution. no doubt there. and a valid alternative to spring-websocket for everybody who prefers it.

speaking for myself, having used both in Grails/Spring apps, spring-websocket just felt/feels more comfortable (my current opinion).

given we are looking at this in a Grails context here, i do not think that Spring "lock-in" is a valid point because the choice of Grails as app framework ties you to Spring in the first place, or lets better say allows you to benefit from what Spring has got to give.