Final deliverables

[keilw]

[desruisseaux]

What is the deliverable content? Only one single module for the API please!!! (do what you want for the implementation).

[keilw]

No actually there is more, see Harold's forwarded mail to us (the Spec Leads)

[desruisseaux]

@keilw I see that the release at https://github.com/unitsofmeasurement/unit-api/releases/tag/2.0 has 2 Jigsaw module (base and format). Can we please rollback to a single Jigsaw module? I don't see any justification for 2 modules: it does not save memory, does not reduce dependencies, does not simplify implementation.

[keilw]

@desruisseaux What do you mean, it's not in the JAR, which says module java.measure.
Those are optional profiles as seen in #42 (which evolving the POM is not a requirement for 2.0) so no need to unwrap anything. Those profiles are for special cases like Industrial IoT where (just helping a similar use case) embedded devices are rarely doing hot deploy via Maven but require the tiniest space. Unless you work in such an environment, just ignore those profiles, but we offer them to those for having well-defined modules there, too.

[desruisseaux]

Ah, sorry I saw src/etc/modules/format/jdk9/module-info.java and though that it would be the modularization to be deployed on Maven central. If this etc directory is only for profiles, then everything is fine - sorry for disturbing.

[keilw]

No worries, yes, it is only for optimized size in very small embedde environments. Where "base" and "format" are often the only ones they need, "quantity" would be an optional module, but the Java Module System only allows "all or nothing". Everything above that speaks for the "full profile".