This is an experimental project to build Vaadin Applications with the Mill Build Tool.
In this early stage we just try to build a Vaadin Application somehow. That means, we don’t follow design concepts typically used in Mill, but instead re-use some shared Vaadin Build Tooling (also used by latest Maven and Gradle plugins) and also use the same directory layout. This means, we can’t use Mills efficient up-to-date checking and caching capabilities.
The reason for this is easy: Vaadin used various tools and also often changes these tools. Some of these tools are simple not designed for being used in isolation (e.g. node/npm/pnpm), and other still have some hardcoded path.
Once we are able to build Vaadin applications in a robust way, I will try to move more and more parts into well-designed and isolated targets. This will be most likely a laborious and incremental path. Any contribution are very welcome!
The idea is to have two separated Mill modules, e.g. a prod submodule.
As development builds will closely work based on node.js, we will make these the default (and only) mode.
Production builds will be slower and don’t need to watch their sources for changes, so we can copy all relevant files to a dedicated location (prod sub-module), where we run the build in production mode.
build.scimport $ivy.`de.tototec::de.tobiasroeser.mill.vaadin::0.0.4`
import de.tobiasroeser.mill.vaadin.VaadinModule
object foo extends JavaModule with VaadinModuleTo stay compatible with Gradle and Maven, our Vaadin project should have the same src/main/{java,resources}-layout. For convenience, you can use mill.scalalib.MavenModule instead of (or in addition too) mill.scalalib.JavaModule (or for Scala: mill.scalalib.SbtModule for mill.scalalib.ScalaModule), which already used this layout.
To
The development of this plugin was initiated and sponsored by iba Consulting Gesellschaft mbH & Co KG.
-
Added support for Mill API 0.11
-
Update Vaadin Flow tooling to 23.3.12
-
Various internal version bumps
Early development stage.
We just try to build a Vaadin Application somehow. That means, we don’t follow design concepts typically used in Mill, but instead re-use some shared Vaadin Build Tooling (also used by latest Maven and Gradle plugins) and also use the same directory layout. This means, we can’t use Mills efficient up-to-date checking and caching capabilities.
