I use Eclipse to create PRs for projects like Jetty 12 which has 200+ Maven
modules. How is this not a problem there?
In Commons, we use the Moditect plugin to generate the JPMS junk, no
problems. No need for the insanity of special test projects.
It feels like we are doing something wrong here... or working _way to hard_.
Gary
On Fri, Aug 9, 2024, 7:10 AM Piotr P. Karwasz <piotr.karw...@gmail.com>
wrote:
> Hi Gary,
>
> On Fri, 9 Aug 2024 at 12:00, Gary Gregory <garydgreg...@gmail.com> wrote:
> >
> > I hope you mean a new maven module and not a whole new git repo...
>
> Unfortunately I mean repo. The problem is that IDEs (even commercial
> ones like IntelliJ IDEA) barely handle JPMS and have big problems with
> the way we generate JPMS module descriptors (via BND).
>
> I tried to:
>
> * create a new module,
> * add a `module-info.java` file to it with content:
>
> ```
> module log4j.test {
> requires java.base;
> requires org.apache.logging.log4j.core;
> }
> ```
>
> The Log4j Core import is inevitably marked as an error and even Maven
> can not build it.
>
> I am afraid we really need a separate Maven Project (i.e. also a
> separate repo) to run those tests. I also don't want to risk having
> false positives, just because Maven decided to use the classpath
> instead of the module path.
>
> Piotr
>
