[sling-whiteboard] branch master updated: typo
This is an automated email from the ASF dual-hosted git repository. bdelacretaz pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git The following commit(s) were added to refs/heads/master by this push: new 1c2c508 typo 1c2c508 is described below commit 1c2c5081e6ee9cc1ad0417fb410558217f34c8aa Author: Bertrand Delacretaz AuthorDate: Thu Apr 1 16:54:43 2021 +0200 typo --- SlingModelPersist/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SlingModelPersist/README.md b/SlingModelPersist/README.md index 7e24a17..13292e4 100644 --- a/SlingModelPersist/README.md +++ b/SlingModelPersist/README.md @@ -1,6 +1,6 @@ SlingModelPersist --- -This module provides transparent persistent for Sling Models. +This module provides transparent persistence for Sling Models. See also https://issues.apache.org/jira/browse/SLING-8450
[sling-whiteboard] branch master updated: typo
This is an automated email from the ASF dual-hosted git repository. bdelacretaz pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git The following commit(s) were added to refs/heads/master by this push: new 6f5e923 typo 6f5e923 is described below commit 6f5e92321d308181db1b12866cacd83c174f6d76 Author: Bertrand Delacretaz AuthorDate: Wed Apr 15 15:06:52 2020 +0200 typo --- graphql-scripting/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/graphql-scripting/README.md b/graphql-scripting/README.md index 35c534c..92d2d8d 100644 --- a/graphql-scripting/README.md +++ b/graphql-scripting/README.md @@ -20,7 +20,7 @@ or turning any Sling Resource into a GraphQL endpoint. See the comments in that Here are my initial rough ideas for evolving this into a useful GraphQL core for Sling: * Use the Sling resolution mechanism to acquire the GraphQL Schemas, using maybe a `.gqlschema` request extension to get them. This provides full flexiblity to generate schemas from scripts, servlets, Sling Models or whatever's needed. We'll probably need to invent a way to specify which `DataFetchers` to use in the schemas. - * (Implemmented in a minimal way - `GraphQLServlet`) Demonstrate how to create a "traditional" GraphQL endpoint by setting up a Sling Resource to define it, which might need a proxy servlet for ease of use. As those endpoints use the Sling script resolution mechanism under the hood, it's possible to define several such endpoints with specific characteristics, schemas etc. if needed. Also, backing those endpoints with Sling Resources allows for setting up access control of them, which w [...] + * (Implemented in a minimal way - `GraphQLServlet`) Demonstrate how to create a "traditional" GraphQL endpoint by setting up a Sling Resource to define it, which might need a proxy servlet for ease of use. As those endpoints use the Sling script resolution mechanism under the hood, it's possible to define several such endpoints with specific characteristics, schemas etc. if needed. Also, backing those endpoints with Sling Resources allows for setting up access control of them, which we [...] This (along with a few "details") would allow for this GraphQL core to be used in various modes:
[sling-whiteboard] branch master updated: typo
This is an automated email from the ASF dual-hosted git repository. bdelacretaz pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git The following commit(s) were added to refs/heads/master by this push: new da88b76 typo da88b76 is described below commit da88b76b6a6756bd28c0dd2157439a3511a6408f Author: Bertrand Delacretaz AuthorDate: Thu Aug 16 11:20:35 2018 +0200 typo --- resource-schemas/README.md | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/resource-schemas/README.md b/resource-schemas/README.md index 0d2c5c2..329f38e 100644 --- a/resource-schemas/README.md +++ b/resource-schemas/README.md @@ -4,13 +4,13 @@ Sling Resource Schemas prototype This is a (very rough for now) prototype using schemas to describe Sling resource types: their data model, actions that can be taken on specific resource types, default content, default access control etc. -The goal is to generate self-describing HTTP APIs as well as a basic (but progressively enhanceable) HTML UI to create content, +The goal is to generate self-describing HTTP APIs as well as a basic (but progressively enhanceable) HTML UI to manage content, based on schemas that describe the content and behavior of resource types in detail. The data part of the schemas aims to use JSON Schema principles, with extensions to define actions, default content, default access control and other non-data aspects. -However, or now schemas are just hardcoded in Java -(in the [DemoSchemas.java](./demo/src/main/java/org/apache/sling/resourceschemas/demo/schemas/DemoSchemas.java) ) +However, for now schemas are just hardcoded in Java +(in [DemoSchemas.java](./demo/src/main/java/org/apache/sling/resourceschemas/demo/schemas/DemoSchemas.java) ) , as the goal is to demonstrate the overall behavior without caring much -about such "details" as how the schemas are defined. at this point. +about such "details" as how the schemas are defined.
[sling-whiteboard] branch master updated: typo
This is an automated email from the ASF dual-hosted git repository.
bdelacretaz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git
The following commit(s) were added to refs/heads/master by this push:
new 3e8abe3 typo
3e8abe3 is described below
commit 3e8abe31b285cc00367b9caa16e9572520e9bd79
Author: Bertrand Delacretaz
AuthorDate: Mon Jul 2 11:36:49 2018 +0200
typo
---
file-optim/README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/file-optim/README.md b/file-optim/README.md
index f423f07..c0fb585 100644
--- a/file-optim/README.md
+++ b/file-optim/README.md
@@ -87,7 +87,7 @@ Additionally, there are two Sling mdoels for discovering the
optimization inform
## Defining a File Optimizer
-File optimizers are used by the library to optimize resources based on the
file mime type. Each File Optimizer should implement the
[FileOptimizer](src/main/java/org/apache/sling/fileoptim/FileOptimizer.java)
interface, setting the *mime.type* property to the MimeTypes for which the
optimizer is applicable. The [Service
Rankin](https://osgi.org/javadoc/r2/org/osgi/framework/Constants.html#SERVICE_RANKING)
property can be used to override the default File Optimizers.
+File optimizers are used by the library to optimize resources based on the
file mime type. Each File Optimizer should implement the
[FileOptimizer](src/main/java/org/apache/sling/fileoptim/FileOptimizer.java)
interface, setting the *mime.type* property to the MimeTypes for which the
optimizer is applicable. The [Service
Ranking](https://osgi.org/javadoc/r2/org/osgi/framework/Constants.html#SERVICE_RANKING)
property can be used to override the default File Optimizers.
@Component(service = FileOptimizer.class, property = {
FileOptimizer.MIME_TYPE + "=image/jpeg" })
public class DevNullFileOptimizer implements FileOptimizer {
[sling-whiteboard] branch master updated: typo
This is an automated email from the ASF dual-hosted git repository. bdelacretaz pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git The following commit(s) were added to refs/heads/master by this push: new e048e77 typo e048e77 is described below commit e048e77e1c46fe9f17410ba2b830d564796699b1 Author: Bertrand Delacretaz AuthorDate: Thu May 24 16:39:23 2018 +0200 typo --- capabilities/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/capabilities/README.md b/capabilities/README.md index 6b2274d..8463344 100644 --- a/capabilities/README.md +++ b/capabilities/README.md @@ -10,7 +10,7 @@ external systems or do anything suitable to check what's available. Each `Probe` multiple values as String key/value pairs. To define a Capabilities endpoint, create a Sling Resource with 1..N properties having -names that end with the `_probe_` suffix. The String value of each property is passed +names that end with the `_probe` suffix. The String value of each property is passed to all available `ProbeBuilder` services, and the first one that returns a `Probe` is used. As an example, with the default Probes found in this module, creating a Resource such as -- To stop receiving notification emails like this one, please contact bdelacre...@apache.org.
[sling-whiteboard] branch master updated: typo
This is an automated email from the ASF dual-hosted git repository. radu pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git The following commit(s) were added to refs/heads/master by this push: new 57479c5 typo 57479c5 is described below commit 57479c563c0b57dd6bc6626c3d5ea12b2a70d4ba Author: Radu Cotescu AuthorDate: Tue Mar 13 09:16:17 2018 +0100 typo --- featuremodel/requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/featuremodel/requirements.md b/featuremodel/requirements.md index b5d61bf..b575039 100644 --- a/featuremodel/requirements.md +++ b/featuremodel/requirements.md @@ -44,7 +44,7 @@ The feature model is about describing a feature, aggregating features to either * SFM250 - It must be possible to mark the additional content as optional. * SFM260 - A feature must be able to specify additional requirements and capabilities that extend the requirements and capabilities from the contained artifacts. * SFM270 - A feature must be able to extend other features. -* SFM280 - A feature must be able to depend on other features through the requirements/capabilities model based on the feature contents. The feature model must be able to deal with circular dependencies. However, there must be now way of explicitly requiring a feature from another feature. +* SFM280 - A feature must be able to depend on other features through the requirements/capabilities model based on the feature contents. The feature model must be able to deal with circular dependencies. However, there must be no way of explicitly requiring a feature from another feature. * SFM290 - The feature model must describe how several features are aggregated to build a higher level feature. This description must include all parts of the feature model (bundles, configurations, framework properties etc.). The description should be general for extension, which means it should describe how extensions are aggregated without requiring the model implementation to know the type of extension. * SFM300 - The feature model must describe how several features are combined to build an application. This description must include all parts of the feature model (bundles, configurations, framework properties etc.). The description should be general for extension, which means it should describe how extensions are aggregated without requiring the model implementation to know the type of extension. * SFM310 - When features are aggregated, either to create a higher level feature or an application, and a bundle/artifact is encountered with different versions, the feature model must be capable of only using the bundle/artifact with the highest version number. The detection is based on the artifact/bundle id, not the bundle symbolic name. -- To stop receiving notification emails like this one, please contact r...@apache.org.
