Eclipse brings a built-in mvn. That's how i run quarkus:dev: create a mvn run-config for "quarkus:dev". It looks like quarkus does not play well with mvn in eclipse, since running a project like that simply does not work for multi-module projects: it fails to start, usually saying it can not inject this or that bean.
Only when i mvn install the whole multi-module project (on the command line) and then restart that eclipse mvn run-config, then it does work.
Forcing me to mvn install - just to run my locally edited code - is forcing me to put jars into my .m2 that are probably buggy (not ready). This will leak into other build work done on that machine (eg unrelated projects relying on the same SNAPSHOT libs).
I'm probably missing something. Any input on this would be great.
jeffmaury
commented
2 years ago
Eclipse brings a built-in mvn. That's how i run quarkus:dev: create a mvn run-config for "quarkus:dev". It looks like quarkus does not play well with mvn in eclipse, since running a project like that simply does not work for multi-module projects: it fails to start, usually saying it can not inject this or that bean.
Only when i mvn install the whole multi-module project (on the command line) and then restart that eclipse mvn run-config, then it does work.
Forcing me to mvn install - just to run my locally edited code - is forcing me to put jars into my .m2 that are probably buggy (not ready). This will leak into other build work done on that machine (eg unrelated projects relying on the same SNAPSHOT libs).
I'm probably missing something. Any input on this would be great.