Re: master simulator build broken on ManagedContext

2013-10-16 Thread Darren Shepherd
The simulator context is removed in the spring modularization branch. The simulator now just had a small spring XML that only has its own config that gets added to the classpath when using the simulator profile. I ran into some issue with DB txns that held up merging the spring modularization

Re: master simulator build broken on ManagedContext

2013-10-09 Thread Prasanna Santhanam
Thanks Darren, the jetty start has chugged along and I'm able to bring up the server. I'd like to not have that orphaned context ideally since it gets left out often this way. But I can live with that for now. On Wed, Oct 09, 2013 at 10:55:58AM -0700, Darren Shepherd wrote: > Prasanna, > > Try no

Re: master simulator build broken on ManagedContext

2013-10-09 Thread Darren Shepherd
Prasanna, Try now. I pushed 0d7aa931b4892661df733cd1ba20fe139d13e59b for this. The issue was that at some point the package of ConfigDepotImpl was changed in some refactoring. The applicationContext was changed for this, but apparently somebody didn't check simulatorContext. The bean should neve

Re: master simulator build broken on ManagedContext

2013-10-09 Thread Darren Shepherd
I'll look at that. Gimme about 15 minutes. Darren On Wed, Oct 9, 2013 at 10:12 AM, Prasanna Santhanam wrote: > Hi, > > on the simulator build in jenkins [1] on starting jetty I see the > following issue: > > ERROR [o.s.w.c.ContextLoader] (main:null) Context initialization failed > org.springfra