You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@sling.apache.org by kw...@apache.org on 2017/02/22 09:16:11 UTC

svn commit: r1783984 - /sling/site/trunk/content/documentation/development/slingstart.mdtext

Author: kwin
Date: Wed Feb 22 09:16:11 2017
New Revision: 1783984

URL: http://svn.apache.org/viewvc?rev=1783984&view=rev
Log:
SLING-6541 document Maven classpath enrichment and possibility to disable that

Modified:
    sling/site/trunk/content/documentation/development/slingstart.mdtext

Modified: sling/site/trunk/content/documentation/development/slingstart.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/slingstart.mdtext?rev=1783984&r1=1783983&r2=1783984&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/slingstart.mdtext (original)
+++ sling/site/trunk/content/documentation/development/slingstart.mdtext Wed Feb 22 09:16:11 2017
@@ -209,6 +209,8 @@ A model can reference other slingstart o
 
 The resulting model is a merged model, starting with the dependencies and then merging in the current model.
 
+By default the Maven classpath is extended by the dependencies of the merged model. This behaviour can be disabled though via setting the parameter `disableExtendingMavenClasspath` to `true` ([SLING-6541](https://issues.apache.org/jira/browse/SLING-6541)).
+
 ## Model Merging
 
 If two or more models are supplied, they are merged feature by feature, each feature being treated as a separate unit.