JNDI is used in log4j-web for being able to locate a LoggingContext or
configuration (forget which), and there's a JNDI lookup in log4j-core.
Might be other places, but those are the main ones I can remember.

Essentially, anything that relies on javax.* other than for some select
crypto and security stuff are not in java.base. See the listing: <
https://docs.oracle.com/javase/9/docs/api/java.base-summary.html>.

On 29 January 2018 at 08:20, Gary Gregory <garydgreg...@gmail.com> wrote:

> On Sun, Jan 28, 2018 at 9:35 PM, Matt Sicker <boa...@gmail.com> wrote:
>
> > That's rather limiting. Here's what we're already using:
> >
> > * java.compiler: annotation processing (could potentially be split, but
> > this situation is already confusing enough for users)
> > * java.management: JMX
> > * java.naming: JNDI
> > * java.scripting: javascript/groovy/etc plugins
> > * java.xml: XML configuration parsing
> >
>
> Also, some low hanging fruits:
>
> * java.sql: for JDBC
> * JMS depends on a Java EE API jar.
>
> Gary
>
>
> > I may have missed some others, but it may be difficult to trim it down to
> > just java.base. Even with some of the simpler ones, we'll end up with
> > several additional modules to detangle that.
> >
> > If we could include multiple logical modules in a single physical module,
> > then this wouldn't be as tedious.
> >
> > On 27 January 2018 at 20:01, Ralph Goers <ralph.go...@dslextreme.com>
> > wrote:
> >
> > > Also, in Java 9 it must only require the java.base module.
> > >
> > > Ralph
> > >
> > > > On Jan 27, 2018, at 6:49 PM, Matt Sicker <boa...@gmail.com> wrote:
> > > >
> > > > On 27 January 2018 at 16:18, Ralph Goers <ralph.go...@dslextreme.com
> >
> > > wrote:
> > > >
> > > >> The requirement is that log4j-core have no required dependencies. I
> > > should
> > > >> have as few optional dependencies as possible.
> > > >>
> > > >
> > > > That sounds perfectly reasonable. LMAX and Jackson are good examples.
> > > >
> > > > --
> > > > Matt Sicker <boa...@gmail.com>
> > >
> > >
> > >
> >
> >
> > --
> > Matt Sicker <boa...@gmail.com>
> >
>



-- 
Matt Sicker <boa...@gmail.com>

Reply via email to