David M. Lloyd
David M. Lloyd
How are we feeling about this, three weeks on? Is this something that we can resolve in documentation (for example)?
Are we ready to resolve this?
If you want to monitor the duration of tasks, then a proxy executor does seem like the way to go, however it might be best to do this at the...
> * JPMS name: Should only the runtime module have a JPMS name (and maybe `spi`), or should every module have one, as proposed? (@dmlloyd) IMO yes (every module should...
> I didn't replace `deployment` with `build.` I like the idea, but it might be too big for Quarkus 3. Additionally, `build` is the output directory of Gradle, so we...
> > AFAIU, this does proposal doesn't introduce a requirement on the api/impl split. It mentions strong and loose coupling as options, with the strong coupling being equivalent to a...
One more thing to add (arguably a bit nitpicky but I keep thinking about it): The word `runtime` actually has multiple meanings. On the one hand, it is an adjective;...
For Surefire we should probably give JVM args. But one thing I'd be concerned about is that today, we might use `--enable-native-access=ALL-UNNAMED`, but in the future it might be e.g....
> > So we should hide this from the user if possible. > > How could one achieve that? In runner jars it's easy to achieve through the manifest entry,...
> For Surefire we should probably give JVM args. But one thing I'd be concerned about is that today, we might use `--enable-native-access=ALL-UNNAMED`, but in the future it might be...