Fri, Nov 30, 2018, 07:44 Hannes H.
> > My precise problem is that some Spring Framework modules reading classes
> > from the package ' org.apache.commons.logging from both commons.logging'
> > and so does 'commons.dbcp2' (which seems to be a module of DBCP). That is
> > appare
2018 15:01:57 +0100, Hannes H. wrote:
> > So there is no common approach planned for Apache Commons?
>
> Recently released components probably have an
> Automatic-Module-Name
> defined for each artefact.
>
> Is there a precise question?
> Do you have a suggestion?
>
So there is no common approach planned for Apache Commons?
Am Fr., 30. Nov. 2018 um 14:50 Uhr schrieb A. Soroka :
> Since each Commons component is released separately, each can have its own
> plan.
>
> ajs6f
>
> On Fri, Nov 30, 2018, 8:46 AM Hannes H.
> > Hi,
> >
p of Components that are
> developed and released individually.
>
> Can you be more specific? Which Components are you talking about?
>
> Gary
>
> On Fri, Nov 30, 2018, 01:52 Hannes H.
> > Good day,
> >
> > while migrating a code base which depends on Apache Common
Good day,
while migrating a code base which depends on Apache Commons from Java 8 to
Java 11 the problem with 'split packages' crossed my efforts to do so.
I did some research but I could not find anything, so I try by asking here:
Is there a modularized version/edition of Apache Commons
