I pushed a fix anyway. 2017-05-10 13:50 GMT+02:00 Pavel <[email protected]>:
> Simon said which configuration must be used. Weld developers said this > configuration > can be set via system settings -Dorg.jboss.weld.bootstrap. > concurrentDeployment=false > so there is no need to modify PAX-CDI code. > > If someone has the same problem he can find more information here: > https://issues.jboss.org/browse/WELD-2383 > > вторник, 9 мая 2017 г., 23:58:57 UTC+3 пользователь Pavel написал: > >> Hi Simon >> >> Thank you very much! This is really helped. But what are the consequences >> of such workaround? >> >> Best regards, Pavel >> >> вторник, 9 мая 2017 г., 18:43:43 UTC+3 пользователь Simon Spero написал: >>> >>> This is probably suboptimal, but it may be good enough: >>> >>> When configuring the weld bootstrap at >>> >>> https://github.com/ops4j/org.ops4j.pax.cdi/blob/master/pax-c >>> di-weld/src/main/java/org/ops4j/pax/cdi/weld/impl/WeldCdiCon >>> tainer.java#L120 >>> >>> it is possible to disable concurrent deployment by chaining >>> .add(ConfigurationKey.CONCURRENT_DEPLOYMENT,"false") >>> >>> That should either solve the deadlock, or move it :) >>> >>> Simon >>> >>> -- > -- > ------------------ > OPS4J - http://www.ops4j.org - [email protected] > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- ------------------------ Guillaume Nodet -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
