Lite/Full split: define packaging/deployment/lifecycle

[Ladicek]

https://github.com/eclipse-ee4j/cdi/blob/864e1b4f779e4d6d5a80f147d975a510446d4987/spec/src/main/asciidoc/core/packagingdeployment_lite.asciidoc

This also affects the "The BeanContainer object" chapter:

https://github.com/eclipse-ee4j/cdi/blob/864e1b4f779e4d6d5a80f147d975a510446d4987/spec/src/main/asciidoc/core/beanmanager_lite.asciidoc

It also affects the "Modularity" chapter:

https://github.com/eclipse-ee4j/cdi/blob/864e1b4f779e4d6d5a80f147d975a510446d4987/spec/src/main/asciidoc/core/injectionandresolution.asciidoc

[manovotn]

This issue seems like it is tightly coupled with #484
As in, we need to establish build compatible extensions because this issue incorporates type and bean discovery process which should mention how it is intertwined with extensions. Same goes for application init and shutdown.

I can try to propose a PR that will address as much as possible WRT this issue but will also leave some TODOs that should be part of #484 because it would be much better to have links to refer to within the build compatible extensions section.

[Ladicek]

They are closely related indeed.

[manovotn]

Was resolved some time ago as part of #546 (and other PRs), we just forgot to close the issue.
Closing now...