On 11 Aug 2004 at 17:24, Jacek Laskowski wrote:
> It seems very similar to what I saw executing the examples. I guess,
> Alex (the author) defined the openejb.home variable somehow and it
> worked fine.
>
> Please try out the examples again, but before performing do the following:
>
> o Add the lines to project.properties of example_02:
>
> openejb.home=${basedir}
>
> o In the same file - project.properties - modify
> maven.junit.sysproperties line so that it contains openejb.home
> variable. It ends up as (all on the same line):
>
> maven.junit.sysproperties=openejb.home openejb.nobanner
> java.naming.factory.initial ##openejb.configuration
>
> o Execute maven db:teardown and start over
>
____________________________________________________
I can confirm that these changes allowed Test 2 to proceed to
successful build.
Yes .. It is important to "teardown" (flush) the DB each time a
change is made to configuration, as pointed out in the article.
Now proceeding to Test 3 and other puzzles ahead.
DL
