Which is really bad later on, as you cannot really determine what version a jar is then.

For me, this is a false issue: • that JAR won't leave your project build unless you explicitly copy it (which means, if you're unsure, just rebuild it) • if you copy it (e.g. using the

application

or

war

plugin), then indeed you lose that hint in the filename, but it's nothing more than a hint, and because it would mean that it comes from the same multi-project build as the final application/war file, you have other means of conveying the version that are better suited IMO • you can include the version inside the JAR (through the manifest or a file) and that would me a much more reliable source than the file name.