Btw, anyone has a clue what the module name for the cdi-2.0 api is? Did not find anything in the published official jar... Am I just blind?
LieGrue, strub > Am 13.03.2020 um 12:31 schrieb Mark Struberg <strub...@yahoo.de>: > > I'd leave genesis-flava for now. We can get rid of it for jakarta.* maybe. > > JPMS has completely failed imo. The adoption rate in the industry is near > zero. > Companies who need a module system use OSGi. The others use flat classpath. > The isolation is a joke. Security wise it's useless. > So the only real benefit we'd have is out-of-the-box compilation with java14. > And for that the MANIFEST.MF entry is enough afaiu. > > LieGrue, > strub > > > >> Am 13.03.2020 um 11:50 schrieb Romain Manni-Bucau <rmannibu...@gmail.com >> <mailto:rmannibu...@gmail.com>>: >> >> There are a few things to take into account I think: >> >> 1. Maybe let's drop genesis completely >> 2. Module info is a pain but still the only way to be jlink compatible, >> automatic name just enables compilation >> >> I'd be to have a classified artifact with module info if we can otherwise >> automatic name is ok. >> >> Le ven. 13 mars 2020 à 11:26, Mark Struberg <strub...@yahoo.de >> <mailto:strub...@yahoo.de>> a écrit : >> hi! >> >> I think half-loud about enhancing flava8 to use the maven-jar plugin to >> automatically provide a module name. >> It defaults to the artifact-id but can be tweaked by each module to include >> a Automatic-Module-Name: entry in manifest.mf. >> >> The reason why I do not like the module-info.class is that this often breaks >> backward compat with many java8 projects. And there are still WAY many >> companies using java8 only... >> >> wdyt? >> >> LieGrue, >> strub >> >
