8.1, Extension Manager support the concept of managed dependencies. Its the same idea than Maven's

support the concept of managed dependencies. Its the same idea than Maven's {{code

and Groovy. The Concept Create a wiki page and transform it into a Wiki Component This Component will only

to use wiki components and Groovy. = The Concept = * Create a wiki page and transform

attachment. Changelog 1.5 XWiki 14.0 Add the concept of original metadata document author. 1.4 XWiki

=== //XWiki 14.0// Add the concept of original metadata document author. === 1.4 === //XWiki 12.0

="ctag:label" content="$detail.getLabel()"><a class="tag-concept-link" href='$detail.getUri()'>$detail.getLabel

.tag-delete').each(this.ajaxTagDelete); // [semtag] concept list for each tag $$('.doc-tags .tag-list-activator').each(this.ajaxTagConcepts); // [semtag] end concept list for each tag

description : See the [[Configuration API>>Extension.Configuration Module]] for general configuration concepts. == Configuration Permissions == It's possible to implement permission checking for ##ConfigurationSource## properties, to decide who has the rights to view or modify them. To implement this check

summary : Extra Configuration APIs related to platform concepts (e.g. user references)

XWiki platform which does not link the user-defined tags to a concept. A semantic tag will preserve the

a.selected-tag:visited { color: #ccc; } .tag-concept-link { padding: 0.5em 2em 0.5em 0; background: url

be considered as a "proof of concept". Due to some design decisions (mainly due to "write on read" for Views

notes : This is initial Proof of Concept.

are created (the concept of a saved filter). Follow the same incremental approach for implementing

. The best way to grasp the concept is to see how it works on the [[References Page

]], either from a tuple of its component fields. = Concepts = Similar to the [[authorization API

of abstraction on top of the existing XWiki concepts, there is no new implementation of the rights

, but those concepts are internal details from the pov of this API and should never be a concern of the caller