Hi. Le mer. 19 juil. 2023 à 13:43, Elliotte Rusty Harold <elh...@ibiblio.org> a écrit : > > 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
I repeat that it has been "Commons policy" for over 15 years. If I missed something, please use concrete examples, based on the modules shipped with v4.0-beta1, so that we can fix it before the "non-beta" release. Thanks, Gilles > > 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 > > > > > [...] --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
