Rob Cernich

I don't have any issues with the information being there. it's easy enough to rm and I don't think it takes up that much space. That said, if we can...

The notion is that a module for kieserver may depend on functionality that is provide by an upstream module. In this case, we don't want to reinstall the module, but...

> If module is required its only checked if exists - so it means, artifacts are not processed, scripts are not executed, module descriptor is not merged? Correct, although it...

The only piece you're missing is that it might already be installed in the base image and is not installed in the build. The kieserver is the best (only?) example...

Perhaps we emit a warning during generation, if a required module is missing, but don't error until the build.

That's fine. At one point, we had talked about including the module source in the images. However, a label would certainly make things easer to view without having to crack...

In addition to documentation, which I think should be part of the tool suite (e.g. like javadoc), I think we should start to consider how we package, distribute and resolve...

I think we follow the spec as defined by atomic. This is a markdown file, so if we can format it well, vi/more/less should be good enough to view the...

I understand that none of this is mandated, but I think it provides a good enough starting point. It would be our responsibility to add this to the image, which...

Maybe we should just have a separate USAGE.md file that describes how to utilize the module, e.g. what it does, how it works, how to extend it, etc.