jstrachan: hi

jstrachan: thx for adding servicemix-utils to the build server

jstrachan: the update of the webapp seems to have been handled ok

yay

np

could the CI server be fixed - the current job will run forever because of a bad commit (from me - sorry - beers and cake is on me if you is near Copenhagen sometime)

:)

which CI server btw

there are more ;) I am only aware of the one public I can reach from the internet - the logicblaze one

:) tend to look at the internal iona ones; then there's the nightly one - haven't looked at bamboo in a while, forgot about that one :)

btw which one pushes the binaries to the apache maven snapshot server?

the nightly cron job (on another box :)

i use that one to verify that my commits are okay on unix as well ;)

restarted bamboo

if restart does it skip to next build number? - trunk-725 is broken

jstrachan: how about adding a -Dmaven.test.failure.ignore=true and run the build with tests on that box?

gertv: sure - wanna be an admin to tinker?

davsclaus: I think it starts a new checkout/build

jstrachan: sure

jstrachan: don't really need it to test this though -- I can just modify the scripts and webapp and let the automatic update do its work

gertv: you talking about bamboo now or the nightly cron?

the nightly cron

yeah - was hoping to get a reliable CI box somewhere - so far bamboo is all we have - they seem to require loads of hand-holding these days due to hanging builds, crashing CI servers and whatnot

is bamboo 2.0 any better?

or use something like continuum on the servicemix zone?

davsclaus: dunno - they all seem to suck :)

gertv: yeah - though continuum is one of the worst I've ever tried to keep running

gertv: so far TeamCity seems the best; but even that needs constant hand-holding usualy

but yeah setting up something on the zone would rock

we are also only on bamboo 1.2 at my current client

couldn't it be "restarted" automatiically once per day - then builds that runs forever will be forced to be quit and it will start up and run again

great idea - though even that seems harder than it looks - I think it needs to be rebooted once a day :)

e.g. to kill all the java procs etc

not sure how to do that on solaris zone

hence reason I was going the EC2 route

but yeah - having the box rebooted daily would be awesome

(so long as the CI tool restarts that is :)

i am sure we are not the only one with this problem - cant the CI providers help?

you would have thought so :)

I guess most folks have small, simple builds - or tests that never hang :)

what about something with wmware? to start from the same image one a day?

then we dont need to make sure it stops nicely!

yeah - great idea

though the servicemix zone is solaris isn't it?

yeah, it is

how about enhancing the cron based solution to suit our needs?

sounds like we can do a better job ourselves ;)

;)

yeah am thinking we kinda use both - ultimately though CI tools are damn handy

I think if we can get one to reboot every day, we're mostly there

ok, let's set that up then -- that shouldn't be rocket science, should it?

what is bamboo running on?

linux

btw i think the camel:run is broken when you dont have spring xml files in META-INF/services or what the default folder is. I am however not 100% sure but recall some issues with it 1-2 weeks ago. Could probably be tested by our examples and move the spring xml files to another location and set the configuration element in the maven pom

yeah - IIRC there's a property you can set to define the URI to load

not sure though :)

yeah we have documented it in the wiki

just recall i have some examples where i have spring xml files in src/main/resources and not the meta-inf folder. and it wont run with camel:run

even for that configuration

i guess i will be safe and create a jira to look into it when we have time - at work now

Hi guys, looks like someone did a thesis on Apache Camel - cool :) http://elib.uni-stuttgart.de/opus/volltexte/2008/3520/pdf/STUD_2127.pdf

Haven't read through it yet though...

interesting :)

Yeah, seems that interest in Camel is spilling over to the academic side of things

they must be attracted to all the innovative stuff that James once in a while crank out at the speed of light ;)

then there there is the humble users that just wants to use camel as a helper to communicate with all the different technologies/frameworks. Its amazing to do this also.

janstey: added it to the articles list http://cwiki.apache.org/ACTIVEMQ/articles.html

so its spans from one end to the other ;)

:)

Yeah, I'm sure there's a few Groovy based thesis' floating around also ;)

;)

And Jetty also ;)

sorry was it melly or what was it in maven 1

jelly :)

hey, any interest in a camel-ldap component?

sure why not

almost got one done

i was also thinking about a camel-webdav to complement our file/ftp component

hadrian what ldap framework are you using? spring-ldap is pretty okay actually

+1

i need that in integrations in the future actually so nice timing ;)

hadrian: sounds good to me

davsclaus: i only have basic javax.naming.directory in the component and apacheds for tests

just that spring-ldap supports configuring multi IPs and it will do failover - maybe that is standard in plain javax.naming

davsclaus: i'll try to write a test using spring-ldap too

we should not reinvent the wheels

btw is IONA represented at the danish conference JAOO in Aarhus next month? I remeber IONA had a stand last year

davsclaus: doesn't look like it -- there's no mention of them on the sponsor page anyway

okay i couldn't find any good speakers so I doubt that I will be there