Ok, don't do that unless it's new code in new packages. Otherwise
you're creating a dependency hell for existing clients. It is
extremely developer hostile. Pretty much all of https://jlbp.dev/
applies but especially

JLBP-5: Do not include a class in more than one classpath entry
JLBP-6: Rename artifacts and packages together

Debugging the problems this will cause is difficult and painful, even
for someone well-versed in Maven dependency management.

On Wed, Jul 19, 2023 at 11:37 AM Dimitrios Efthymiou
<efthymiou.dimitri...@gmail.com> wrote:
>
> no. I mean creating maven modules inside commons-math, like
> the existing ones:
> commons-math-neuralnet
> commons-math-transform
>
> On Wed, 19 Jul 2023 at 12:29, Elliotte Rusty Harold <elh...@ibiblio.org>
> wrote:
>
> > Could you be precise about what you mean by "modularisation"? It's a
> > very overloaded term. Do you mean Java 9 modules as defined by the
> > JPMS?
> >
> > On Wed, Jul 19, 2023 at 12:33 AM Dimitrios Efthymiou
> > <efthymiou.dimitri...@gmail.com> wrote:
> > >
> > > Hello everyone. Is there, or gonna be, a dedicated ticket for the
> > > modularisation of all 14 packages commons-math-legacy has? I think that
> > > some of them are easy to modularise like optimisation, special and filter
> >
> >
> >
> > --
> > Elliotte Rusty Harold
> > elh...@ibiblio.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >



-- 
Elliotte Rusty Harold
elh...@ibiblio.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to