I'm not sure that actually fixes it. I rebuilt TomEE myself with your changes in there, and I can not get the old behavior with the TomEE Maven Plugin. (I also rebuilt the plugin, plus all of TomEE).
I still am seeing the data directory created in the working directory for TomEE instead of where I am launching the command. Maybe this is a tomee-m-p problem? On Mon, Apr 28, 2014 at 7:28 PM, Thiago Veronezi <[email protected]> wrote: > Hi, > > Please let me know if this change fixes the issue. > http://svn.apache.org/viewvc/tomee/tomee/trunk/container/openejb-core/src/main/resources/default.openejb.conf?r1=1590837&r2=1590836&pathrev=1590837 > > []s, > Thiago > > > On Mon, Apr 28, 2014 at 5:41 PM, Thiago Veronezi <[email protected]>wrote: > >> Hi, >> I guess I am the one to blame. :) >> Thanks for reporting it. I will revert that change asap. >> []s, >> Thiago >> On Apr 28, 2014 5:24 PM, "jieryn" <[email protected]> wrote: >> >>> I've noticed a change in behavior today, the default data source is >>> now writing to a local directory instead of where Maven is invoked. >>> >>> So, earlier in the week I could run mvn tomee:run and it would by >>> default create a HSQLDB in the $CWD/data/ directory. Now it is in >>> target/apache-tomee/data/ directory. Additionally, an executable war >>> built by TomEE is moving the data directory to be under .distribution/ >>> directory. This is very problematic because the .distribution >>> directory is removed quite easily by the executable war itself.. >>> >>
