2009/7/8 Rafael Schloming <[email protected]>: > Aidan Skinner wrote: >> >> On Wed, Jul 8, 2009 at 2:35 PM, Rafael Schloming<[email protected]> >> wrote: >> >>> Aidan Skinner wrote: >>>> >>>> On Wed, Jul 8, 2009 at 2:26 PM, Rafael Schloming<[email protected]> >>>> wrote: >> >>>>> Why can't the java profile just do the same thing? >>>> >>>> Lack of --data-dir. We should probably add that though. :) >>> >>> Yes, especially if it would make the java profiles stop dumping things >>> like >>> derby.log and derbyDB outside the build dir. ;) >> >> I thought I'd beaten that out of DerbyMessageStore. Are you still >> seeing that running with java-derby? > > It's definitely dumping derby.log into the root of the tree. It's possible > that the derbyDB dir was leftover from a while back. I've removed it and > will let you know if it reappears.
We have the ability to load a java broker configuration and modify it. I would argue that we don't need a --data-dir option but simply need to load the configuraiton file and set the work property to be the value that would be set for --data-dir. The config-systest-derby.xml just needs to have the environment-path setup so it writes its files there by default rather than defaulting to up QPID_WORK from the system properties. This brings me back to the Change in DerbyMessageStore to pick up QPID_WORK directly which I don't agree this is correct. if the environment path is not set for Derby then the broker should fail to start up. Martin > --Rafael > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Martin Ritchie --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
