We haven’t found a plugin to generate the CFG files (property files in our case) - they’re created by hand. Luckily they don’t change much - that’s why the rename thing for semantic versioning will be a royal pain.
I sympathize with the issues you’re having with CamelBlueprintTestSupport - until recently, it’s been very problematic with the race conditions. Since the last set of fixes went in, I haven’t had any issues. Note that the Camel archetype for blueprint used to generate a bad configuration in the POM that caused me a lot of grief. I submitted a PR and it was merged into 2.17-SNAPSHOT, but you could use that and then change the Camel version in the POM and get a good start. That said, by using the Java RouteBuilders, we can test our routes using CamelTestSupport and get around all those CamelBlueprintTestSupport issues. We’re working on some integration tests as well using Pax Exam, so we’ll only be using CamelBlueprintTestSupport during development - we won’t care so much if those test fail in our CI builds. The one thing about camel-scr I don’t particularly like is all the annotations - it really muddies-up the code. They are only used by the maven-scr-plugin to generate a beans.xml file. I think I’d rather build this file using maven filters or something. Also, watch out for the version of the maven-scr-plugin you use - I don’t remember which version it was, but one of the newer ones didn’t work (a beans.xml file wasn’t generated). > On Jan 29, 2016, at 12:55 PM, Ranx <[email protected]> wrote: > > Thanks for the insights. It sounds as if the cfg files would need a form of > semantic versioning then like bundles use. Obviously my insights are > limited. Do you create your configuration files via the maven plugin and > install them in etc with a feature? That might obviate some of the pain. > > I'd have to look a bit closer at it. I do like what I see of it. I get > tired of XML fingerfehlers causing CBTS to hang with the rather nebulous > "Gave up waiting for CamelContext" errors. I'm also an old Java hack so > prefer it anyway. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-SCR-tp5776954p5777014.html > Sent from the Camel - Users mailing list archive at Nabble.com.
