Re: Issue with qualified exports

Would it not be better to provide an option for people who need to do this level of validation so that there might be an option such as —validate-module-presence=B instead to make it possible to get the validation, but not have to do this for common, simple developer builds, but it could be

Re: Issue with qualified exports

On 07/21/2016 10:55 AM, Alan Bateman wrote: On 21/07/2016 09:14, Peter Levart wrote: Also, While it is expected that qualified exports are mostly used among modules that are more tightly coupled and are therefore more likely compiled together, some tools that invoke compiler (for example

Re: Issue with qualified exports

Also, While it is expected that qualified exports are mostly used among modules that are more tightly coupled and are therefore more likely compiled together, some tools that invoke compiler (for example Maven), have a strategy to compile one module at a time, incrementally building the

Re: Issue with qualified exports

Hi, A "middle-ground" solution could be for javac to have yet another option, for example: --add-phantom-module=B Since the compiler invoker explicitly named the module, javac can validate the qualified exports of other modules against this name too. If both the exporting module

Re: Issue with qualified exports

I agree, this is not very module like if we are building dependencies to export targets. This is another reason, for me, that this feels wrong. I am just not sure I understand why we care so deeply for “authorization” to use code when there are so many (nearly countless) ways to exploit the

Re: Issue with qualified exports

Thank you Alex. Sounds like good advice. I'll raise it over there. Thanks for chatting with me about it. Cheers, Paul On Wed, Jul 20, 2016 at 6:37 PM, Alex Buckley wrote: > Since A does not require B, you are quite right that the compiler doesn't > need B to compile A

Re: Issue with qualified exports

Alex, I must respectfully disagree with your analogy. We both agree that it is good for the compiler to check an "import" statement. I imagine we would also both agree that checking "requires" is good too. I would argue what makes this good is because the developer has the intention of locating

Re: Issue with qualified exports

On 7/20/2016 3:07 PM, Paul Benedict wrote: Currently I am writing a module that another team will consume. Let's just call these modules A and B. Module A must export its packages to Module B and B alone. For reasons beyond my control, I do not have access to Module B. However, I don't need to

Issue with qualified exports

My build is build 9-ea+125-2016-07-08-164610.javare.5260.nc Currently I am writing a module that another team will consume. Let's just call these modules A and B. Module A must export its packages to Module B and B alone. For reasons beyond my control, I do not have access to Module B. However,