Le ven. 20 oct. 2023 à 21:48, Adam Cimarosti a écrit :
> I don't think I can really split things into a different modile as the
> plugin writes binaries to the /target/classes directory for inclusion in
> the jar file.
>
This is not a blocker if you aggregate in a 3rd module.
> Could you go i
I don't think I can really split things into a different modile as the
plugin writes binaries to the /target/classes directory for inclusion in
the jar file.
Could you go into more details on what would be involved in a custom life
cycle?
Would you have some pointers for this (class names, docs,
Hi,
did you try splitting rust and java code in 2 modules and using
-T$something ? would do it, otherwise you probably need to write an
extension which will capture compiler config, make it skipped to replace it
but a custom lifecycle management in your own plugin but looks more
complicated to ach
Hello,
I am the author of the rust-maven-plugin (
https://github.com/questdb/rust-maven-plugin/).
We use this plugin ourselves at QuestDB and in CI `mvn compile` takes
around 8 minutes.
It appears that the Java and Rust builds happen serially.
Is there a way to parallelise things so our plugin
