Closed geemang2000 closed 13 years ago
The reason is current Spring version in Grails. I wanted it to be compatible to the release version. Once Grails upgrade to the latest Spring and will match the one used by Camel I'll upgrade them.
In the meantime you can always force the use of the latest Camel if you so desire using the Grails' dependency DSL in BuildConfig.groovy.
Hope it helps.
Best regards, Matthias.
2011/8/30 geemang2000 < reply@reply.github.com>
Are there any plans to update this plugin to use the newer Camel versions? Is there a reason to stay with Camel 2.5?
Reply to this email directly or view it on GitHub: https://github.com/padcom/grails-routing/issues/1
Makes good sense. With Grails 2.0 we'll likely see an updated set of Camel libs?
I hope so :) I'm waiting on some beta release of Grails 2.0 to re-work the plugin so that it works with latest Apache Camel. For now it's just to unstable to do anything serious with it.
I'm using your plugin in a Grails RC2 project. I cloned the grails-routing project and modified the BuildConfig.groovy as follows. So far so good....
grails.project.class.dir = "target/classes"
grails.project.test.class.dir = "target/test-classes"
grails.project.test.reports.dir = "target/test-reports"
grails.project.dependency.resolution = {
// inherit Grails' default dependencies
inherits("global") {
// uncomment to disable ehcache
// excludes 'ehcache'
}
log "warn" // log level of Ivy resolver, either 'error', 'warn', 'info', 'debug' or 'verbose'
repositories {
grailsPlugins()
grailsHome()
grailsCentral()
// uncomment the below to enable remote dependency resolution
// from public Maven repositories
mavenLocal()
mavenCentral()
//mavenRepo "http://snapshots.repository.codehaus.org"
//mavenRepo "http://repository.codehaus.org"
//mavenRepo "http://download.java.net/maven/2/"
//mavenRepo "http://repository.jboss.com/maven2/"
}
dependencies {
// specify dependencies here under either 'build', 'compile', 'runtime', 'test' or 'provided' scopes eg.
build('org.apache.camel:camel-core:2.8.2')
build('org.apache.camel:camel-spring:2.8.2') {
excludes 'spring-aop', 'spring-beans', 'spring-core', 'spring-expression', 'spring-asm', 'spring-tx', 'spring-context'
}
runtime('org.apache.camel:camel-groovy:2.8.2') {
excludes 'spring-context', 'spring-aop', 'spring-tx', 'groovy-all'
}
runtime('org.apache.camel:camel-stream:2.8.2')
test('org.apache.camel:camel-test:2.8.2') {
excludes 'junit'
}
}
}
with that said... we might target http://camel.apache.org/2011/11/12/apache-camel-290-rc1-released.html as I believe they are in sync with the new Springs libs just as Grails 2 is.
I promise I'll take a look at it today in the evening.
Matthias.
2011/12/1 geemang2000 < reply@reply.github.com
with that said... we might target http://camel.apache.org/2011/11/12/apache-camel-290-rc1-released.html as I believe they are in sync with the new Springs libs just as Grails 2 is.
Reply to this email directly or view it on GitHub: https://github.com/padcom/grails-routing/issues/1#issuecomment-2976415
I'll gladly help, just say the word
Hi guys,
I've done some preparation for the Camel upgrade process. I'd like you to take a peak at what is and what is not working in regard to your test cases. Here's how you can setup the environment for testing the latest version.
You can alternatively check if all the dependencies are properly fetched by creating a WAR achive and examining its WEB-INF/lib folder.
Unfortunatelly the 2.9 RC Camel version that's available on project's site still uses the 3.0.6 version of Spring which means that there will be a possible glitch in versions. Let's just hope it'll be small enough or that the 2.9 version will ship with Spring 3.1...
Let me know if you'll run into any issues. If there will be no feedback I'll release 1.1.4 in 2-3 days (with the dependency to Grails 2.0.0.RC2 probably or if RC3 will be out by that time).
Best regards, Matthias.
2011/12/1 geemang2000 < reply@reply.github.com
I'll gladly help, just say the word
Reply to this email directly or view it on GitHub: https://github.com/padcom/grails-routing/issues/1#issuecomment-2977945
Thanks Matthias, I'll try it out. Sorry about the mixup on Spring Versions, I was wrong on that.
FYI: Trying to spure up support for Spring 3.1 http://camel.465427.n5.nabble.com/DISCUSS-Camel-2-9-release-td5038092.html#a5039933
Yeah.. I don't think they're going to go for it in 2.9 GA - maybe in 2.9.1 as the Spring dependency is still in RC phase and will go into GA together with Grails (I hope).
M.
2011/12/1 geemang2000 < reply@reply.github.com
Thanks Matthias, I'll try it out. Sorry about the mixup on Spring Versions, I was wrong on that.
FYI: Trying to spure up support for Spring 3.1
http://camel.465427.n5.nabble.com/DISCUSS-Camel-2-9-release-td5038092.html#a5039933
Reply to this email directly or view it on GitHub: https://github.com/padcom/grails-routing/issues/1#issuecomment-2980734
So far working good with my app. Using camel test and netty components.
Guys, I'll be releasing 1.1.4 final the day Grails 2.0 goes final. I hope this will not slow you down or anything. If you want you can always use the 1.1.4-SNAPSHOT released a few days back that'll be pretty much identical to the final one. Unless of course Graeme and co. make some changes that'll force me to update but I don't expect that at this point.
Good with me.
Looks like Camel 2.9 is GA, time to update BuildConfig dependencies
http://camel.apache.org/2012/01/01/apache-camel-290-released.html
True, true :) Will do in the evening - thanks for the info!
Are there any plans to update this plugin to use the newer Camel versions? Is there a reason to stay with Camel 2.5?