From 3d0c9c1f1d9866f5df1369674f878596913d8a00 Mon Sep 17 00:00:00 2001
From: Ron Smeral <rsmeral@redhat.com>
Date: Mon, 2 Mar 2015 14:23:23 +0100
Subject: [PATCH] DELTASPIKE-846 Docs: Clarify that scheduler module has manual
 dependencies

---
 .../src/main/asciidoc/scheduler.adoc          | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/documentation/src/main/asciidoc/scheduler.adoc b/documentation/src/main/asciidoc/scheduler.adoc
index 5e2a9990e..ad11560fb 100644
--- a/documentation/src/main/asciidoc/scheduler.adoc
+++ b/documentation/src/main/asciidoc/scheduler.adoc
@@ -43,6 +43,27 @@ By default, the Scheduler module looks to integrate with Quartz. If this is the
 </dependency>
 ----
 
+=== 3. Declare Container Control dependency
+
+Scheduled jobs can have built-in CDI contexts started for the duration of their execution using `@Scheduled#startScopes` which internally uses the <<container-control#, Container Control module>>. The dependency on the API and the appropriate implementation needs to be declared manually even if the feature is not used. An example for the Weld implementation:
+
+[source,xml]
+----
+<dependency>
+    <groupId>org.apache.deltaspike.cdictrl</groupId>
+    <artifactId>deltaspike-cdictrl-api</artifactId>
+    <version>${deltaspike.version}</version>
+    <scope>compile</scope>
+</dependency>
+
+<dependency>
+    <groupId>org.apache.deltaspike.cdictrl</groupId>
+    <artifactId>deltaspike-cdictrl-weld</artifactId>
+    <version>${deltaspike.version}</version>
+    <scope>runtime</scope>
+</dependency>
+----
+
 == Use the Module Features
 
 === @Scheduled