Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grails 2.4.3 compatibility #25

Open
ph4t opened this issue Sep 15, 2014 · 11 comments
Open

Grails 2.4.3 compatibility #25

ph4t opened this issue Sep 15, 2014 · 11 comments

Comments

@ph4t
Copy link

ph4t commented Sep 15, 2014

We get the following exception after installing the plugin:

...\spring-batch-2.0.0\grails-app\services\grails\plugins\springbatch\SpringBatchService.groovy: 248: Method 'onApplicationEvent' from class 'grails.plugins.springbatch.SpringBatchService' does not override method from its superclass or interfaces but is annotated with @Override.
 @ line 248, column 2.

Is this a known issue?

@ph4t ph4t changed the title Grails 2.4.3 compability Grails 2.4.3 compatibility Sep 15, 2014
@danieldbower
Copy link
Collaborator

Did a little bit of research just now. I'm coding against Grails 2.2.4, but with a small timebox, I downloaded Grails 2.4.3. The Interface for ApplicationListener, which is used by the SpringBatchService appears not to have changed from the docs that I can tell, but I encountered the same error as you when I tried to install the plugin on an otherwise blank project.

I've committed the change, but not released as of yet.

You might want to checkout another branch https://github.com/xmlking/grails-spring-batch which has some additional functionality for 2.4.3. I simply don't have the cycles to invest in bringing that over currently.

@michaelbannister
Copy link

I, too, would be interested getting the plugin working with the latest Grails release.

I simply don't have the cycles to invest in bringing that over currently.

Is there anything in particular that needs doing? I'd be happy to try & help – I haven't worked on Grails plugins before but I'm always ready to learn something new :)

@danieldbower
Copy link
Collaborator

At this point, I think there are branches floating around with the plugin working with the latest Release. All that needs done is pulling the changes in, and pushing to the master grails plugin repository. This just involves getting the proper permissions to this repo and the grails plugin repository, and performing the push.

@johnrengelman
Copy link
Collaborator

@danieldbower can you post to the grails-dev Google Group requesting permissions publish permissions for this plugin? You'll need to provide 'grails.org' username. Let me know when you do, then I'll respond back approving it and they should give you access to do publications.

@danieldbower
Copy link
Collaborator

@johnrengelman
Copy link
Collaborator

Looks like it was approved.

@john-london
Copy link

@danieldbower @johnrengelman Did you have any success in publishing the 2.4.3 updates please? I see the official version plugin hasn't been updated since Sep 2014, pre-dating the fixes for the latest Grails version.

@danieldbower
Copy link
Collaborator

I am able to publish, but I haven't had the time/funding to properly test it before pushing. Has anyone started to run this in a Grails 2.4 environment to smoke out any bugs?

@john-london
Copy link

@danieldbower I have been using the version shown here (https://github.com/xmlking/grails-spring-batch) as mentioned in your post for 2.4.3. It seems to work ok. However, there appears to be a very nasty bug / mode of behaviour, that I expect is common to all versions, when this plugin is used in a plugin itself. Details here: #29 (I see you closed #27 as a dupe).

I'd be happy to work on a fix for this, but I'm still relatively new to Grails/Groovy. At the moment, I'm looking at ideas mentioned here: http://stackoverflow.com/questions/24028410/load-spring-beans-from-custom-groovy-files-in-grails-app.

Update: I've posted a possible fix in the comments to #29 and I'd be interested in any comments thereon (have yet to test it fully).

@danieldbower
Copy link
Collaborator

@john-london: With @xmlking's branch, at what commit did you pull? Have you tested the admin screens to verify they still work: being able to start/stop a job, viewing when steps last ran, etc...

@john-london
Copy link

I used the latest commit on master, but am not using (and so have not tested) any of the UI screens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants