Thanks, Kabir, I will have a look at it. Currently, I have this vague idea that this maven plugin to be written should be a specialized version of the maven-assembly-plugin, restricted to handling modules (as in jboss modules, not maven modules) only. On the other hand, MODULES-3 seems to suggest a solution where this maven plugin should simply take an existing directory-based module repository and turn it into a jar-based repository. This, however, strikes me as not very maven-like.
IMHO, the optimal solution would actually comprise two maven plugins:
1. A maven plugin that provides a new packaging type, e.g. "module", for composing a module. Since directories cannot be published to a maven repository the module thus created needs to be compressed, e.g. zipped.
2. A maven plugin that takes a set of dependencies that are modules and creates a module repository from it, either directory-based or jar-based.
Does this look like a viable solution?
On the other hand, I'm not sure if there is indeed a need for such a maven plugin, or such maven plugins. As a matter of fact, I used the maven-assembly-plugin for creating a jar-based repository, and encountered no major obstacles. Implementing the plugins suggested above should be doable and fun yet is there really a need for them?