Vasilis Nicolaou

> Don't know, how common it is, but Mill currently does not support creating WARs out of the box, but Spring Initializr does have an option to select "JAR" or...

### mill init from gradle project In contrast with generating a maven project with https://start.spring.io/ , initialising a gradle one has one additional hiccup for `mill init` The gradle effective...

another issue I've found is while mill cli works properly for compile and test ``` Mill version SNAPSHOT is different than configured for this directory! Configured version is 1.0.6 (/home/vnicolaou/mill/example/springboot/java/2-web-socket-initializr/build.mill)...

> > > Yes, you can enable it with `spring.aot.enabled` flag to `true` even if not building a GraalVM native image. > > > > > > You mean `mvn...

started the work [here](https://github.com/com-lihaoyi/mill/pull/6208)

it looks like if `checkGradleModules` is true bom is not working , for example with: ```scala def kotlinSymbolProcessorsResolved: T[Seq[PathRef]] = Task { defaultResolver().classpath( kotlinSymbolProcessors(), boms = allBomDeps() ) } ```...

from my side, I can either introduce a workaround, with a ksp dedicated resolver that has gradle modules disabled or start looking into coursier . A third option is to...

> So [coursier/coursier#3534](https://github.com/coursier/coursier/pull/3534) should fix that, after a coursier release, and coursier version bump here ah nice, thank you! if we had that default in kotlinmodule and pass it to...

> > ah nice, thank you! if we had that default in kotlinmodule and pass it to the resolver, it would also fix it , right? (just out of interest)...

there's a new version that fixes both issues (+ the [gradle rejects](https://github.com/coursier/coursier/issues/3538)), thanks @alexarchambault