desruisseaux commented on PR #12745: URL: https://github.com/apache/maven/pull/12745#issuecomment-5314642130
Thanks @Hiteshsai007 for the reply. I suspected that it was for providing different classpaths at compile-time versus runtime. But it is a complication for Java modules. We would need to specify that for dependencies placed on the module-path, the distinction between `api` and `compile` scope is ignored and all of them are transitive in all circumstances. This feature would be for classspath projects only. This is admittedly a lot of projects, but aren't we creating a technical debt when an alternative (in progress) could be to try to make Java modules more attractive to developers by making them easier to use? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
