Björn Michael

JUnit 5.10 provides a _org.junit.jupiter.api.extension._`InvocationInterceptor` that allows to start a _Mockito Session_ before constructor of the test class is called. E.g. ``` class StrictMockingExtension implements InvocationInterceptor, AfterEachCallback { public T...

In https://github.com/eclipse-tycho/tycho/commit/72747e79e8ad9bc6ee556cac11bdc2e262ce6db2 `org.eclipse.sisu.equinox.launching.internal.P2ApplicationLauncher` has been removed.

As a workaround we could split our build into a "p2" build and "tycho" build and could circumvent the tycho version dependence.

Is there a kind of post-configurer for Beans like the following fictional example to separate bean instantiation from initialization? ``` @Configuration public class JavaConfig { @Bean public PaymentProcesser paymentProcessor(){ return...

> Should I try tackling the stuff mentioned in [#6944 (comment)](https://github.com/google/guava/issues/6944#issuecomment-1914342198) as well? Thank you for your effort. It would suffice to provide `com.google.common.io.CharStreams.asInputStream(Reader, Charset): InputStream` without changing `CodingErrorAction`s of...

I can give it a try.

It is very welcome if Eclipse developers can also benefit from the JSpecify annotations right from the start. They can be used e.g. in [JDT Null analysis](https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-using_null_annotations.htm) in addition to...

I have no objection to your suggestion - sounds good.

I'm also interested in a solution to register certain `ArgumentConverter`s _project wide_. What occurs very often is - Class to Instance conversion via default constructor e.g. ``` @ValueSource(classes = {...

One use case would be to enable `org.mockito.junit.jupiter.MockitoExtension` from [`org.mockito:mockito-junit-jupiter`](https://github.com/mockito/mockito/tree/main/subprojects/junit-jupiter) globally by default. This would activate strict stubbing then. https://github.com/mockito/mockito/issues/769.