Proposal: #VersionedDependences

Ali Ebrahimi ali.ebrahimi1781 at
Fri Jan 27 19:08:29 UTC 2017


On Fri, Jan 27, 2017 at 9:49 PM, <forax at> wrote:

> Hi Ali,
> ------------------------------
> Why we don't add source code support for version string in module
> declaration?
> module foo at 1.0{
> ....
> }
> module bar at 2.0{
> ....
> }
> This way when code reviewing we know what is version of module.
>  Also, we don't have Remi's mentioned problem of multi-module code bases.
> when you do things like security patch by example, you may update several
> module versions but want only to commit the change corresponding to the
> security fix,
> i.e. not having the security fix hidden in the middle of a lot of
> module-info useless updates.
> In my opinion, it's close to inserting the source control version inside a
> code, it's an anti-pattern.
This is some thing that currently occurring in modular code bases before
java9 in Maven based code bases and version strings recorded in mvn.xml
Anyway, command line options can override source code values.


Best Regards,
Ali Ebrahimi

More information about the jpms-spec-observers mailing list