You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project needs an automatic module name (or a proper module descriptor). My suggestion would be org.apache.commons.logging.
Background: normally the module name would be automatically derived from the JAR name, or the group/artifact. But that gives commons.logging.jboss.logging or org.jboss.logging.commons.logging.jboss.logging, respectively, neither of which are good names.
Since this module is a drop-in replacement for the Apache project, its automatic module name should be the same so that dependency resolution will find the replacement library at run time. The upstream project uses the automatic module name of org.apache.commons.logging; so should we.
The text was updated successfully, but these errors were encountered:
This project needs an automatic module name (or a proper module descriptor). My suggestion would be
org.apache.commons.logging
.Background: normally the module name would be automatically derived from the JAR name, or the group/artifact. But that gives
commons.logging.jboss.logging
ororg.jboss.logging.commons.logging.jboss.logging
, respectively, neither of which are good names.Since this module is a drop-in replacement for the Apache project, its automatic module name should be the same so that dependency resolution will find the replacement library at run time. The upstream project uses the automatic module name of
org.apache.commons.logging
; so should we.The text was updated successfully, but these errors were encountered: