Scopes in the Jigsaw module system

[Daniel Latrémolière]

> Imagine that java.beans module provides @GenerateBeanInfo annotation 
> to be placed on any JavaBean class and generate appropriate BeanInfo 
> class automatically rather than requiring it to be code manually. If I 
> correctly understood, the associated GenerateBeanInfoProcessor should 
> be placed in a separate java.beans.processor module. How will the 
> javac know that whenever somebody uses @GenerateBeanInfo annotation in 
> own code the java.beans.processor module must be consulted during 
> compilation? 
Wouldn't it be possible to use custom scopes: an annotation processor 
will provide scopes with some mapped to "annotation-processor" and 
"execution", to implement his contract of annotation processor.

How many scopes for generated bytecode? By example an XSLT stylesheet 
loaded with xsltc (like in OpenJDK) will be transformed dynamically in 
bytecode without compilation (javac) step.

How many scopes for weaved modules, by example with AspectJ or OpenJPA? 
Will weaver change the module-info.class to add the dependency to his 
runtime library in execution scope?

I can understand one scope (execution), many scopes (the custom steps, 
and that is what I am using with Ivy), but I have a problem with two and 
only two scopes.

cf. section "Different concepts" on Ivy configurations against Maven scopes:
http://ant.apache.org/ivy/m2comparison.html

Sorry for being boring,
Daniel.