Gail,
About the issue you had with ByteBuddy + the SM, I opened
https://hibernate.atlassian.net/browse/HHH-12932 . I have a (simple) fix
for it ready.
--
Guillaume
On Mon, Aug 27, 2018 at 3:52 PM Guillaume Smet
wrote:
> So, the system properties are not considered when running with the
> secu
To clarify, `/hibernate.properties` (at root of class path) will work.
That one (if exists) is always read during boot.
On Mon, Aug 27, 2018 at 9:14 AM Chris Cranford wrote:
> Technically the -D parameter should work; however I know a
> hibernate.properties file works.
>
> On 08/24/2018 11:54 PM
So, the system properties are not considered when running with the security
manager.
Log says:
Could not copy system properties, system properties will be ignored
And the code is the following:
try {
Properties systemProperties = System.getProperties();
// Must be thread-safe in case an a
Better to use WildFly -secmgr option, instead of -Dsecurity.manager.
From what I recall, this helps avoid a boot time issue with
-Dsecurity.manager.
For enabling javassist for a one off test run, simply prestart your
WildFly app server with the desired options and then launch.
For more than a
Technically the -D parameter should work; however I know a
hibernate.properties file works.
On 08/24/2018 11:54 PM, Gail Badner wrote:
> I tried running:
>
> mvn clean test -Dtest=HibernateNativeAPINaturalIdTestCase
> -Dhibernate.bytecode.provider=javassist -Dsecurity.manager=true
>
> The result i
Let me check what is happening here.
There are 2 issues: the test should work with ByteBuddy. At least, it did
work a few weeks ago when I worked on this. And we should be able to
override the bytecode provider. It also worked a few weeks ago as I tested
Javassist and ByteBuddy.
And IIRC, I used
Hi Gail,
mvn clean test -Dtest=HibernateNativeAPINaturalIdTestCase
-Dextra.server.jvm.args="-Dhibernate.bytecode.provider=javassist"
-Dsecurity.manager=true
should do it. But I still see ByteBuddy in the stacktrace. I also tried to
add property directly to WildFly configuration file or to hiberna
Since there was no objections, I re-enabled BlueOcean.
See an example here:
http://ci.hibernate.org/blue/organizations/jenkins/hibernate-search-6-poc/detail/HSEARCH-3239/142/pipeline
When in the BlueOcean interface, you can go back to the classic interface
using the button circled in red in this
The original message was received at Mon, 27 Aug 2018 15:37:37 +0800
from lists.jboss.org [15.9.202.182]
- The following addresses had permanent fatal errors -
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.o
