Right. "openjpa.loglevel=WARN" is just converted to "-
Dopenjpa.Log=DefaultLevel=WARN".
It'd be nice if you could just specify the latter from the console,
but unfortunately surefire doesn't propagate system properties
through to the forked Surefire test runner, so we need to special-
cas
> Running mvn "-Dopenjpa.Log=openjpa ( DefaultLevel=WARN )" -
> Dopenjpa.loglevel=WARN install
> seems to work to set the level in the two different maven tasks,
> although I'm confused why there are two different properties used to
> control the log messages.
>
> Any ideas?
The -Dopenjpa.lo
Hi,
mvn test -Dopenjpa.loglevel=WARN
Thanks for that, Patrick. When I use this, two things happen, as
below. Using "-Dopenjpa.Log=openjpa ( DefaultLevel=WARN )" turns off
the INFO logging messages from the [resources:resources] part of the
maven task. Apparently this isn't affected by th
mvn test -Dopenjpa.loglevel=WARN, I believe.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and
