Skip to content
This repository has been archived by the owner on Dec 2, 2021. It is now read-only.

[grails4] NoClassDefFoundError on startup #14

Open
longwa opened this issue Feb 27, 2019 · 6 comments
Open

[grails4] NoClassDefFoundError on startup #14

longwa opened this issue Feb 27, 2019 · 6 comments
Assignees

Comments

@longwa
Copy link

longwa commented Feb 27, 2019

Grails 4.0.0.M1

Looks like the QuartzService is using the defunct grails.transaction.Transactional which has been removed in Grails 4.

This causes a NoClassDefFoundError on startup in Grails 4.

java.lang.NoClassDefFoundError: grails/transaction/GrailsTransactionTemplate
        at com.agileorbit.schwartz.QuartzService.init(QuartzService.groovy)
        at com.agileorbit.schwartz.QuartzService$init.call(Unknown Source)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:119)
        at com.agileorbit.schwartz.SchwartzGrailsPlugin.doWithApplicationContext(SchwartzGrailsPlugin.groovy:77)

I think it should be using grails.gorm.transactions.Transactional instead.

@erichelgeson erichelgeson self-assigned this Jun 13, 2019
@robertoschwald
Copy link
Contributor

There is much more to migrate for Grails 4.0.0. Hibernate Mappings, etc. has gone in Hibernate 5.

@longwa
Copy link
Author

longwa commented Jul 15, 2019 via email

@robertoschwald
Copy link
Contributor

robertoschwald commented Jul 15, 2019

@erichelgeson started to port to Grails4 already. Havn‘t checked the status of it, yet.

@longwa
Copy link
Author

longwa commented Jul 15, 2019 via email

@erichelgeson
Copy link
Member

erichelgeson commented Jul 15, 2019

I have a Grails 4 branch https://github.com/agileorbit/grails-schwartz/tree/eric/grails4 with it mostly working - 1 test failing right now. I chose to remove the automated changelog generation as it used many liquibase/hibernate methods that are now gone. Also while a nice feature, not critical for a M1 release.

I'll ping @bobbywarner and see if we can push a M1 from my branch so people can get testing and temp ignore the 1 test failure (which may just be a race condition in the test)

@erichelgeson
Copy link
Member

FYI there's a 2.0.0.RC1 published now. Please let me know!

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

No branches or pull requests

3 participants