You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by fp...@apache.org on 2019/08/28 09:51:13 UTC
[unomi] branch master updated: [UNOMI-243] Can't clone repository
This is an automated email from the ASF dual-hosted git repository.
fpapon pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/unomi.git
The following commit(s) were added to refs/heads/master by this push:
new c3d2d8f [UNOMI-243] Can't clone repository
new 3042c35 Merge pull request #97 from fpapon/UNOMI-243
c3d2d8f is described below
commit c3d2d8f9198fd33f9ebfd1307925ef0f22c0b4db
Author: Francois Papon <fp...@apache.org>
AuthorDate: Wed Aug 28 10:44:09 2019 +0200
[UNOMI-243] Can't clone repository
---
manual/src/main/asciidoc/5-min-quickstart.adoc | 2 +-
manual/src/main/asciidoc/building-and-deploying.adoc | 2 +-
manual/src/main/asciidoc/configuration.adoc | 2 +-
manual/src/main/asciidoc/consent-api.adoc | 2 +-
manual/src/main/asciidoc/custom-extensions.adoc | 6 +++---
manual/src/main/asciidoc/index.adoc | 2 +-
manual/src/main/asciidoc/recipes.adoc | 4 ++--
manual/src/main/asciidoc/request-examples.adoc | 2 +-
manual/src/main/asciidoc/samples/twitter-sample.adoc | 14 +++++++-------
manual/src/main/asciidoc/useful-unomi-urls.adoc | 4 ++--
10 files changed, 20 insertions(+), 20 deletions(-)
diff --git a/manual/src/main/asciidoc/5-min-quickstart.adoc b/manual/src/main/asciidoc/5-min-quickstart.adoc
index 9a8b7f9..0e5fc4e 100644
--- a/manual/src/main/asciidoc/5-min-quickstart.adoc
+++ b/manual/src/main/asciidoc/5-min-quickstart.adoc
@@ -22,7 +22,7 @@ JAVA_HOME variable https://docs.oracle.com/cd/E19182-01/820-7851/inst_cli_jdk_ja
4) Launch ElasticSearch using : `bin/elasticsearch`
-5) Download Apache Unomi here : http://unomi.incubator.apache.org/download.html
+5) Download Apache Unomi here : https://unomi.apache.org/download.html
6) Start it using : `./bin/karaf`
diff --git a/manual/src/main/asciidoc/building-and-deploying.adoc b/manual/src/main/asciidoc/building-and-deploying.adoc
index 03e80e2..cf34343 100644
--- a/manual/src/main/asciidoc/building-and-deploying.adoc
+++ b/manual/src/main/asciidoc/building-and-deploying.adoc
@@ -29,7 +29,7 @@
==== Building
-. Get the code: `git clone https://git-wip-us.apache.org/repos/asf/incubator-unomi.git`
+. Get the code: `git clone https://github.com/apache/unomi.git`
. Change to the top level directory of Apache Unomi source distribution.
. Run
+
diff --git a/manual/src/main/asciidoc/configuration.adoc b/manual/src/main/asciidoc/configuration.adoc
index 81a04d0..9392d7e 100644
--- a/manual/src/main/asciidoc/configuration.adoc
+++ b/manual/src/main/asciidoc/configuration.adoc
@@ -37,7 +37,7 @@ the values in the `$MY_KARAF_HOME/etc/custom.system.properties`. See the next se
You might want to use environment variables to change the default system configuration, especially if you intend to run
Apache Unomi inside a Docker container. You can find the list of all the environment variable names in the following file:
-https://github.com/apache/incubator-unomi/blob/master/package/src/main/resources/etc/custom.system.properties
+https://github.com/apache/unomi/blob/master/package/src/main/resources/etc/custom.system.properties
If you are using Docker Container, simply pass the environment variables on the docker command line or if you are using
Docker Compose you can put the environment variables in the docker-compose.yml file.
diff --git a/manual/src/main/asciidoc/consent-api.adoc b/manual/src/main/asciidoc/consent-api.adoc
index fef63ec..ee6107d 100644
--- a/manual/src/main/asciidoc/consent-api.adoc
+++ b/manual/src/main/asciidoc/consent-api.adoc
@@ -193,6 +193,6 @@ Upon receiving this event, Apache Unomi will trigger the modifyAnyConsent rule t
----
As we can see this rule is pretty simple it will simply execute the modifyConsentAction that is implemented by the
-https://github.com/apache/incubator-unomi/blob/9f1bab437fd93826dc54d318ed00d3b2e3161437/plugins/baseplugin/src/main/java/org/apache/unomi/plugins/baseplugin/actions/ModifyConsentAction.java[ModifyConsentAction Java class]
+https://github.com/apache/unomi/blob/9f1bab437fd93826dc54d318ed00d3b2e3161437/plugins/baseplugin/src/main/java/org/apache/unomi/plugins/baseplugin/actions/ModifyConsentAction.java[ModifyConsentAction Java class]
This class will update the current visitor profile to add/update/revoke any consents that are included in the event.
\ No newline at end of file
diff --git a/manual/src/main/asciidoc/custom-extensions.adoc b/manual/src/main/asciidoc/custom-extensions.adoc
index 3ac0aae..cb170e4 100644
--- a/manual/src/main/asciidoc/custom-extensions.adoc
+++ b/manual/src/main/asciidoc/custom-extensions.adoc
@@ -345,7 +345,7 @@ content:
You can note here the `actionExecutorId` that corresponds to the `actionExecutor` in the JSON file.
-The implementation of the action is available here : https://github.com/apache/incubator-unomi/blob/master/extensions/lists-extension/actions/src/main/java/org/apache/unomi/lists/actions/AddToListsAction.java[org.apache.unomi.lists.actions.AddToListsAction]
+The implementation of the action is available here : https://github.com/apache/unomi/blob/master/extensions/lists-extension/actions/src/main/java/org/apache/unomi/lists/actions/AddToListsAction.java[org.apache.unomi.lists.actions.AddToListsAction]
==== Custom conditions
@@ -415,6 +415,6 @@ src/main/resources/OSGI-INF/blueprint/blueprint.xml
You can find the implementation of the two classes here :
-* https://github.com/apache/incubator-unomi/blob/master/plugins/baseplugin/src/main/java/org/apache/unomi/plugins/baseplugin/conditions/MatchAllConditionESQueryBuilder.java[org.apache.unomi.plugins.baseplugin.conditions.MatchAllConditionESQueryBuilder]
-* https://github.com/apache/incubator-unomi/blob/master/plugins/baseplugin/src/main/java/org/apache/unomi/plugins/baseplugin/conditions/MatchAllConditionEvaluator.java[org.apache.unomi.plugins.baseplugin.conditions.MatchAllConditionEvaluator]
+* https://github.com/apache/unomi/blob/master/plugins/baseplugin/src/main/java/org/apache/unomi/plugins/baseplugin/conditions/MatchAllConditionESQueryBuilder.java[org.apache.unomi.plugins.baseplugin.conditions.MatchAllConditionESQueryBuilder]
+* https://github.com/apache/unomi/blob/master/plugins/baseplugin/src/main/java/org/apache/unomi/plugins/baseplugin/conditions/MatchAllConditionEvaluator.java[org.apache.unomi.plugins.baseplugin.conditions.MatchAllConditionEvaluator]
diff --git a/manual/src/main/asciidoc/index.adoc b/manual/src/main/asciidoc/index.adoc
index f611a7a..96c5609 100644
--- a/manual/src/main/asciidoc/index.adoc
+++ b/manual/src/main/asciidoc/index.adoc
@@ -22,7 +22,7 @@ Apache Software Foundation
:numbered:
:homepage: https://unomi.apache.org
-image::incubator-logo.png[pdfwidth=35%,align=center]
+image::asf_logo_url.png[pdfwidth=35%,align=center]
== Quick start
diff --git a/manual/src/main/asciidoc/recipes.adoc b/manual/src/main/asciidoc/recipes.adoc
index 7a9e6af..84d8c26 100644
--- a/manual/src/main/asciidoc/recipes.adoc
+++ b/manual/src/main/asciidoc/recipes.adoc
@@ -45,7 +45,7 @@ EOF
The `requiredProfileProperties` and `requiredSessionProperties` are properties that take an array of property names
that should be retrieved. In this case we use the wildcard character '*' to say we want to retrieve all the available
-properties. The structure of the JSON object that you should send is a JSON-serialized version of the http://unomi.incubator.apache.org/unomi-api/apidocs/org/apache/unomi/api/ContextRequest.html[ContextRequest]
+properties. The structure of the JSON object that you should send is a JSON-serialized version of the http://unomi.apache.org/unomi-api/apidocs/org/apache/unomi/api/ContextRequest.html[ContextRequest]
Java class.
Note that it is also possible to access a profile's data through the /cxs/profiles/ endpoint but that really should be
@@ -183,7 +183,7 @@ EOF
==== How to search for profile events
Sometimes you want to retrieve events for a known profile. You will need to provide a query in the body of the request
-that looks something like this (and https://unomi.incubator.apache.org/rest-api-doc/#1768188821[documentation is available in the REST API]) :
+that looks something like this (and https://unomi.apache.org/rest-api-doc/#1768188821[documentation is available in the REST API]) :
[source]
----
diff --git a/manual/src/main/asciidoc/request-examples.adoc b/manual/src/main/asciidoc/request-examples.adoc
index a534acc..d4afd5a 100644
--- a/manual/src/main/asciidoc/request-examples.adoc
+++ b/manual/src/main/asciidoc/request-examples.adoc
@@ -63,7 +63,7 @@ EOF
The `requiredProfileProperties` and `requiredSessionProperties` are properties that take an array of property names
that should be retrieved. In this case we use the wildcard character '*' to say we want to retrieve all the available
-properties. The structure of the JSON object that you should send is a JSON-serialized version of the http://unomi.incubator.apache.org/unomi-api/apidocs/org/apache/unomi/api/ContextRequest.html[ContextRequest]
+properties. The structure of the JSON object that you should send is a JSON-serialized version of the http://unomi.apache.org/unomi-api/apidocs/org/apache/unomi/api/ContextRequest.html[ContextRequest]
Java class.
==== Sending events using the context servlet
diff --git a/manual/src/main/asciidoc/samples/twitter-sample.adoc b/manual/src/main/asciidoc/samples/twitter-sample.adoc
index 16330ec..ccd2828 100644
--- a/manual/src/main/asciidoc/samples/twitter-sample.adoc
+++ b/manual/src/main/asciidoc/samples/twitter-sample.adoc
@@ -107,7 +107,7 @@ We will look at the details of the context request and response later.
==== HTML page
-The code for the HTML page with our Tweet button can be found at https://github.com/apache/incubator-unomi/blob/master/wab/src/main/webapp/index.html[https://github.com/apache/incubator-unomi/blob/master/wab/src/main/webapp/index.html].
+The code for the HTML page with our Tweet button can be found at https://github.com/apache/unomi/blob/master/wab/src/main/webapp/index.html[https://github.com/apache/unomi/blob/master/wab/src/main/webapp/index.html].
This HTML page is fairly straightforward: we create a tweet button using the Twitter API while a Javascript script performs the actual logic.
@@ -265,15 +265,15 @@ The `tweetEvent` event type is not defined by default in Unomi. This is where ou
In order to react to `tweetEvent` events, we will define a new Unomi rule since this is exactly what Unomi rules are supposed to do. Rules are guarded by conditions and if these
conditions match, the associated set of actions will be executed. In our case, we want our new
- https://github.com/apache/incubator-unomi/blob/master/samples/tweet-button-plugin/src/main/resources/META-INF/cxs/rules/incrementTweetNumber.json[`incrementTweetNumber`] rule to only react to `tweetEvent` events and
+ https://github.com/apache/unomi/blob/master/samples/tweet-button-plugin/src/main/resources/META-INF/cxs/rules/incrementTweetNumber.json[`incrementTweetNumber`] rule to only react to `tweetEvent` events and
we want it to perform the profile update accordingly: create the property types for our custom properties if they don't exist and update them. To do so, we will create a
custom
- https://github.com/apache/incubator-unomi/blob/master/samples/tweet-button-plugin/src/main/resources/META-INF/cxs/actions/incrementTweetNumberAction.json[`incrementTweetNumberAction`] action that will be triggered any time our rule matches. An action is some custom code that is deployed in the context server and can access the
+ https://github.com/apache/unomi/blob/master/samples/tweet-button-plugin/src/main/resources/META-INF/cxs/actions/incrementTweetNumberAction.json[`incrementTweetNumberAction`] action that will be triggered any time our rule matches. An action is some custom code that is deployed in the context server and can access the
Unomi API to perform what it is that it needs to do.
===== Rule definition
-Let's look at how our custom https://github.com/apache/incubator-unomi/blob/master/samples/tweet-button-plugin/src/main/resources/META-INF/cxs/rules/incrementTweetNumber.json[`incrementTweetNumber`] rule is defined:
+Let's look at how our custom https://github.com/apache/unomi/blob/master/samples/tweet-button-plugin/src/main/resources/META-INF/cxs/rules/incrementTweetNumber.json[`incrementTweetNumber`] rule is defined:
[source,json]
----
@@ -311,7 +311,7 @@ Finally, we specify a list of actions that should be performed as consequences o
===== Action definition
-Let's now look at our custom https://github.com/apache/incubator-unomi/blob/master/samples/tweet-button-plugin/src/main/resources/META-INF/cxs/actions/incrementTweetNumberAction.json[`incrementTweetNumberAction`] action type definition:
+Let's now look at our custom https://github.com/apache/unomi/blob/master/samples/tweet-button-plugin/src/main/resources/META-INF/cxs/actions/incrementTweetNumberAction.json[`incrementTweetNumberAction`] action type definition:
[source,json]
----
@@ -331,7 +331,7 @@ Finally, we provide a mysterious `actionExecutor` identifier: `incrementTweetNum
===== Action executor definition
-The action executor references the actual implementation of the action as defined in our https://github.com/apache/incubator-unomi/blob/master/samples/tweet-button-plugin/src/main/resources/OSGI-INF/blueprint/blueprint.xml[blueprint definition]:
+The action executor references the actual implementation of the action as defined in our https://github.com/apache/unomi/blob/master/samples/tweet-button-plugin/src/main/resources/OSGI-INF/blueprint/blueprint.xml[blueprint definition]:
[source,xml]
----
@@ -357,7 +357,7 @@ In standard Blueprint fashion, we specify that we will need the `profileService`
===== Action executor implementation
-Our action executor definition specifies that the bean providing the service is implemented in the https://github.com/apache/incubator-unomi/blob/master/samples/tweet-button-plugin/src/main/java/org/apache/unomi/samples/tweet_button_plugin/actions/IncrementTweetNumberAction.java[`org.apache.unomi.samples.tweet_button_plugin.actions
+Our action executor definition specifies that the bean providing the service is implemented in the https://github.com/apache/unomi/blob/master/samples/tweet-button-plugin/src/main/java/org/apache/unomi/samples/tweet_button_plugin/actions/IncrementTweetNumberAction.java[`org.apache.unomi.samples.tweet_button_plugin.actions
.IncrementTweetNumberAction`] class. This class implements the Unomi `ActionExecutor` interface which provides a single `int execute(Action action, Event event)` method: the executor gets the action instance to execute along with the event that triggered it, performs its work and returns an integer status corresponding to what happened as defined by public constants of the `EventService` interface of Unomi: `NO_CHANGE`, `SESSION_UPDATED` or `PROFILE_UPDATED`.
Let's now look at the implementation of the method:
diff --git a/manual/src/main/asciidoc/useful-unomi-urls.adoc b/manual/src/main/asciidoc/useful-unomi-urls.adoc
index a091576..468793c 100644
--- a/manual/src/main/asciidoc/useful-unomi-urls.adoc
+++ b/manual/src/main/asciidoc/useful-unomi-urls.adoc
@@ -54,12 +54,12 @@ Important : all URLs are relative to the private Apache Unomi URL, by default: h
|/cxs/profiles/sessions/SESSION_ID/events
|GET
-|Listing events for a session. This query can have additional such as eventTypes, q (query), offset, size, sort. See the https://unomi.incubator.apache.org/rest-api-doc/#1019321624[related
+|Listing events for a session. This query can have additional such as eventTypes, q (query), offset, size, sort. See the https://unomi.apache.org/rest-api-doc/#1019321624[related
section in the REST API] for details.
|/cxs/events/search
|POST
-|Listing events for a profile. You will need to provide a query in the body of the request that looks something like this (and https://unomi.incubator.apache.org/rest-api-doc/#1768188821[documentation is available in the REST API]) :
+|Listing events for a profile. You will need to provide a query in the body of the request that looks something like this (and https://unomi.apache.org/rest-api-doc/#1768188821[documentation is available in the REST API]) :
{ "offset" : 0,
"limit" : 20,
"condition" : {