Paullo612

Results 14 comments of Paullo612

Thanks for workaround for Gradle, but what about Maven? Tried ```xml ... ... io.micronaut micronaut-http-server provided ``` ```xml ... ... org.apache.maven.plugins maven-compiler-plugin io.micronaut micronaut-http-server ${micronaut.core.version} ``` ```xml ... ... org.apache.maven.plugins...

This should not brake anything, as I've left RxJava 2 as default Reactive Streams implementation. The only thing I'm not sure about is removal of `@Controller` from generated interfaces. Haven't...

Fixed this [here](https://github.com/Paullo612/LinuxJavaFixes). SWT (eclipse) support is possibly broken by javassist update, so, no pull request.

Yes. `native-image` is still named `native-image.cmd` in latest GraalVM CE release: ![Image](https://github.com/user-attachments/assets/34d73e9e-c3ec-4550-ab70-35edaf6ec7cb) And profile is still activated by existence of `${env.JAVA_HOME}/bin/native-image`: https://github.com/micronaut-projects/micronaut-platform/blob/3771c7633b0d456ebd92db9b0cf0cf52415858ff/parent/src/pom-template.xml#L52-L77

It would also be good to have an option to make qualifier construction lazy: ```java @CustomScoped class MyBean { //... } // No custom scope context @Any(reduce=MyQualifier.class, lazy=true) private Provider...

I can use `@Factory` with `InjectionPoint` api, but it is not so trivial to implement: ```java interface MyProvider extends Provider { } @Factory MyProviderFactory { @Prototype MyProvider create(InjectionPoint injectionPoint, BeanContext...

Then I'll have to introduce new Provider type for each new Qualifier. Anyway, I have implementation of this feature (no tests for now, but I've tested it against by codebase)....

[Here it is](https://github.com/Paullo612/micronaut-core/tree/dynamic-qualifiers).

Yes. I ended up with something like ```java public interface RegexQualifierProvider extends Provider { } @Bean class RegexQualifierProviderImpl implements RegexQualifierProvider { private final Argument argument; private final BeanLocator beanLocator; @Inject...

@Saljack, you can use following `jni-config.json` ```json [ { "name":"sun.net.dns.ResolverConfigurationImpl", "fields":[ {"name":"os_searchlist"}, {"name":"os_nameservers"} ] } ] ``` in conjunction with `--initialize-at-run-time=sun.net.dns.ResolverConfigurationImpl` as workaround.