You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by jieryn <ji...@gmail.com> on 2014/04/28 23:23:53 UTC

Apache TomEE 1.6.1-SNAPSHOT

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..

Re: Apache TomEE 1.6.1-SNAPSHOT

Posted by Romain Manni-Bucau <rm...@gmail.com>.
Looks the expected behavior (
http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/java/org/apache/openejb/resource/jdbc/plugin/HsqldbDataSourcePlugin.java).
We should just add a system property if hsqldb doesnt have one like
derby
Le 29 avr. 2014 04:51, "jieryn" <ji...@gmail.com> a écrit :

> 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 <th...@veronezi.org>
> 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 <thiago@veronezi.org
> >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" <ji...@gmail.com> 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..
> >>>
> >>
>

Re: Apache TomEE 1.6.1-SNAPSHOT

Posted by jieryn <ji...@gmail.com>.
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 <th...@veronezi.org> 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 <th...@veronezi.org>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" <ji...@gmail.com> 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..
>>>
>>

Re: Apache TomEE 1.6.1-SNAPSHOT

Posted by Thiago Veronezi <th...@veronezi.org>.
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 <th...@veronezi.org>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" <ji...@gmail.com> 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..
>>
>

Re: Apache TomEE 1.6.1-SNAPSHOT

Posted by Thiago Veronezi <th...@veronezi.org>.
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" <ji...@gmail.com> 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..
>