But that means that the dependency is actually required at runtime.
Looks to me there are 2 options:
- make that dependency a requirement
- restructure your code so it can be a static requirement
One of the benefits I do like about the modularization is that it forces
you to do clean coding. It is a new way of thinking and it looks like your
project has potential to be optimized for that.
thanks,
Robert
On Thu, 12 Apr 2018 13:19:34 +0200, Roman Grigoriadi
<roman.grigori...@gmail.com> wrote:
Hi Robert,
I don't think my case is suitable for requires static / optional. Runtime
will fail with ClassNotFound exception if classes are neither on CP or
MP.
Roman
On Thu, Apr 12, 2018 at 12:46 PM, Martin Desruisseaux <
martin.desruisse...@geomatys.com> wrote:
Hello Robert
Le 11/04/2018 à 18:45, Robert Scholte a écrit :
> I am not aware of such problem. Did you create a Jira[1] issue for it?
>
Done: https://issues.apache.org/jira/browse/MCOMPILER-336
Thanks
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
