On 02/08/16 08:21, charbel yazbeck wrote:
> most of the open sources jars have classes with unnamed package, like
> nar-maven-plugin.
Hmm, citation needed for that I think.
In my experience it is extremely rare for production code to place
classes in the unnamed module. It is extremely bad practice to do so
because it invites name space clashes. I'm astonished that someone
thought it was ok to do this in a maven plugin. But then again ...
> Any idea how can i solve this? Do i have to implement my own version of
> ModuleFinder?
Getting the owner of the jar to release a new jar with the class in a
sensible package is a far better solution.
If you really have to use such a jar then I guess you can always use the
maven shade plugin to generate a variant that has contains the offending
class(es) in a suitably named module. But that's probably not going to
be a great solution when you are trying to use the maven plugin from
maven (chicken and egg issues?) -- I guess you will need to deploy your
own fixed variant in a suitable repo before consuming it in your project.
regards,
Andrew Dinn
-----------
Senior Principal Software Engineer
Red Hat UK Ltd
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander
