[
https://issues.apache.org/jira/browse/EMAIL-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Petrovicky updated EMAIL-186:
-----------------------------------
Description:
At the moment, `commons-email` is a thorn in one's side when it comes to JPMS.
At the very least, it should give a [stable automatic module
name|http://branchandbound.net/blog/java/2017/12/automatic-module-name/] in the
JAR file's manifest.
I can provide a PR fixing this, but judging by the state of EMAIL-183, this
project looks like it is dead and people should instead be discouraged from
using it.
was:
At the moment, `commons-email` is a thorn in one's side when it comes to JPMS.
At the very least, it should give a [stable automatic module
name|[http://branchandbound.net/blog/java/2017/12/automatic-module-name/]] in
the JAR file's manifest.
I can provide a PR fixing this, but judging by the state of EMAIL-183, this
project looks like it is dead and people should instead be discouraged from
using it.
> Commons Email does not provide automatic module name
> ----------------------------------------------------
>
> Key: EMAIL-186
> URL: https://issues.apache.org/jira/browse/EMAIL-186
> Project: Commons Email
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Lukas Petrovicky
> Priority: Critical
> Fix For: 1.6
>
>
> At the moment, `commons-email` is a thorn in one's side when it comes to
> JPMS. At the very least, it should give a [stable automatic module
> name|http://branchandbound.net/blog/java/2017/12/automatic-module-name/] in
> the JAR file's manifest.
> I can provide a PR fixing this, but judging by the state of EMAIL-183, this
> project looks like it is dead and people should instead be discouraged from
> using it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
