This is an automated email from the ASF dual-hosted git repository.
mibo pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/olingo-site.git
The following commit(s) were added to refs/heads/main by this push:
new c791437 Update some links to https
c791437 is described below
commit c791437065a02c2ef5b2282f111f3a9ad12dcc4e
Author: Arnout Engelen <[email protected]>
AuthorDate: Wed Dec 21 15:45:22 2022 +0100
Update some links to https
---
content/contribute.md | 2 +-
content/doc/javascript/project-release.md | 24 ++++++++++++------------
content/doc/javascript/project-setup.md | 2 +-
content/doc/odata2/dependencies.md | 2 +-
content/doc/odata2/eclipse.md | 2 +-
content/doc/odata2/maven.md | 4 ++--
content/doc/odata2/release.md | 28 ++++++++++++++--------------
content/doc/odata2/sample-setup.md | 6 +++---
content/doc/odata2/tomcat.md | 8 ++++----
content/doc/odata4/dependencies.md | 2 +-
content/doc/odata4/eclipse.md | 2 +-
content/doc/odata4/index.md | 6 +++---
content/doc/odata4/maven.md | 4 ++--
content/doc/odata4/release.md | 28 ++++++++++++++--------------
content/doc/odata4/sample-setup.md | 2 +-
content/doc/odata4/tomcat.md | 6 +++---
content/download.md | 6 +++---
content/index.md | 2 +-
content/support.md | 8 ++++----
content/verification.md | 8 ++++----
theme/apache/templates/base.html | 18 +++++++++---------
21 files changed, 85 insertions(+), 85 deletions(-)
diff --git a/content/contribute.md b/content/contribute.md
index 924848f..2210c34 100644
--- a/content/contribute.md
+++ b/content/contribute.md
@@ -75,7 +75,7 @@ To clone the current master branch of the Olingo project
please use one of the f
#### Providing bugfix / code
To provide a bug fix, checkout the current master branch of the project and
develop your solution. In Olingo we truly believe in tests, so your
contribution should at least contain tests that show that your contribution
works as expected and also tests that reproduces the previous reported bug. If
you provide a new feature your tests should reach at least 80 percent
test-coverage.
-To ensure this we have lots of tests and use
[Cobertura](http://cobertura.github.io/cobertura/) as *code coverage tool*. In
addition there exists separate build jobs on the Apache Build servers for
latest versions of [Olingo
V2](https://builds.apache.org/job/olingo-odata2-cobertura/) and [Olingo
V4](https://builds.apache.org/job/olingo-odata4-cobertura/).
+To ensure this we have lots of tests and use
[Cobertura](https://cobertura.github.io/cobertura/) as *code coverage tool*. In
addition there exists separate build jobs on the Apache Build servers for
latest versions of [Olingo
V2](https://builds.apache.org/job/olingo-odata2-cobertura/) and [Olingo
V4](https://builds.apache.org/job/olingo-odata4-cobertura/).
To append your contribution to a JIRA ticket, please create a patch file as
explained in the chapter.
diff --git a/content/doc/javascript/project-release.md
b/content/doc/javascript/project-release.md
index 1b3e468..f2062a6 100644
--- a/content/doc/javascript/project-release.md
+++ b/content/doc/javascript/project-release.md
@@ -7,13 +7,13 @@ Title: Javascript Release Documentation
### Introduction
This document describes the release guidelines for Apache Olingo OData Client
for JavaScript (referenced in this document as ODataJS).
-This is similar to [standard Apache procedures to
release](http://maven.apache.org/developers/release/apache-release.html)
+This is similar to [standard Apache procedures to
release](https://maven.apache.org/developers/release/apache-release.html)
for Maven based projects at Apache, but since it is an JavaScript library it
is adopted to be used with grunt js.
### Build Environment
-Apache Olingo is built and released with [Node.js®](http://nodejs.org/) in
combination with
-[grunt task runner](http://gruntjs.com/)
+Apache Olingo is built and released with [Node.js®](https://nodejs.org/) in
combination with
+[grunt task runner](https://gruntjs.com/)
### Release Artifacts
@@ -152,7 +152,7 @@ The release candidate artifacts:
- Maven artifacts will be staged on repository.apache.org. A new staging repo
is created per RC and will be communicated upon release.
- Distribution commodity packages are staged at
-http://people.apache.org/~[username]/olingo4/js/[version] (e.g.
http://people.apache.org/~mibo/olingo4/js/4.0.0-RC01)
+https://people.apache.org/~[username]/olingo4/js/[version] (e.g.
https://people.apache.org/~mibo/olingo4/js/4.0.0-RC01)
Once candidate artifacts are available, release manager kicks off the [VOTE
process][2].
@@ -165,7 +165,7 @@ If the release candidate gets approved, we can proceed to
release publishing.
This checklist helps verifying if a release candidate is valid:
-* Are all files on "http://people.apache.org/~[username]/olingo4/js/[version]";?
+* Are all files on
"https://people.apache.org/~[username]/olingo4/js/[version]";?
* Check if md5, sha512 and asc files are filled correctly?
* Can the zip files be unpacked without issues?
* Execute a "grunt build"
@@ -185,9 +185,9 @@ If the release candidate gets approved, we can proceed to
release publishing:
- Publish final release Version to [Apache
Repository](https://repository.apache.org/)
- Copy the release Artifacts into the *Staging Area*
- From *Staging Area* close and release the staged Artifacts to finish
publishing
- - Afterwards the Maven artifacts are automatically synced to [Maven
Central](http://search.maven.org/#search|ga|1|org.apache.olingo).
+ - Afterwards the Maven artifacts are automatically synced to [Maven
Central](https://search.maven.org/#search|ga|1|org.apache.olingo).
- Release candidate commodity packages are synced (together with their
checksum and
-signatures) to [Apache Distributions](http://www.apache.org/dist/olingo/).
+signatures) to [Apache Distributions](https://www.apache.org/dist/olingo/).
- Release tag is renamed to final version.
- Release branch is created.
- Release is closed in Jira.
@@ -195,7 +195,7 @@ signatures) to [Apache
Distributions](http://www.apache.org/dist/olingo/).
### Maintain Version Section in DOAP File
-[http://olingo.apache.org/doap_Olingo.rdf][3]
+[https://olingo.apache.org/doap_Olingo.rdf][3]
Results are shown here:
@@ -210,7 +210,7 @@ Results are shown here:
[1]: /documentation.html
[3]: /doap_Olingo.rdf
- [4]: http://projects.apache.org/indexes/alpha.html#O
- [5]: http://www.apache.org/dev/release.html
- [6]: http://www.apache.org/dev/release-publishing.html
- [7]: http://www.apache.org/dev/publishing-maven-artifacts.html
+ [4]: https://projects.apache.org/indexes/alpha.html#O
+ [5]: https://www.apache.org/dev/release.html
+ [6]: https://www.apache.org/dev/release-publishing.html
+ [7]: https://www.apache.org/dev/publishing-maven-artifacts.html
diff --git a/content/doc/javascript/project-setup.md
b/content/doc/javascript/project-setup.md
index 2c19feb..4ba209a 100644
--- a/content/doc/javascript/project-setup.md
+++ b/content/doc/javascript/project-setup.md
@@ -74,7 +74,7 @@ Default are the environment variables *HTTP_PROXY* and
*http_proxy* for **proxy*
##### Java #####
-If you want to run the Apache release audit tools ([Apache
Rat™](http://creadur.apache.org/rat/) ) please perform the
+If you want to run the Apache release audit tools ([Apache
Rat™](https://creadur.apache.org/rat/) ) please perform the
following steps:
* Navigate to
diff --git a/content/doc/odata2/dependencies.md
b/content/doc/odata2/dependencies.md
index 4043d34..135695b 100644
--- a/content/doc/odata2/dependencies.md
+++ b/content/doc/odata2/dependencies.md
@@ -49,4 +49,4 @@ To use the JPA Processor Extension following dependencies are
required:
${olingo.version} == the concrete version of the library. See also:
* [Download Page](/doc/odata2/download.html)
-* [Maven Central](http://search.maven.org/#search|ga|1|org.apache.olingo)
+* [Maven Central](https://search.maven.org/#search|ga|1|org.apache.olingo)
diff --git a/content/doc/odata2/eclipse.md b/content/doc/odata2/eclipse.md
index 75aa307..d9bf171 100644
--- a/content/doc/odata2/eclipse.md
+++ b/content/doc/odata2/eclipse.md
@@ -4,7 +4,7 @@ Title: Eclipse
---
-[Eclipse](http://eclipse.org) (in version `Juno` and `Kepler`) is supported by
the project.
+[Eclipse](https://eclipse.org) (in version `Juno` and `Kepler`) is supported
by the project.
With the Maven project files can be generated with:
diff --git a/content/doc/odata2/maven.md b/content/doc/odata2/maven.md
index 7af8a70..0d24ad2 100644
--- a/content/doc/odata2/maven.md
+++ b/content/doc/odata2/maven.md
@@ -27,6 +27,6 @@ to run the build, execute JUnit tests and create all
artifacts.
Further information to Git and Maven is available here:
-* http://git-scm.com/
-* http://maven.apache.org
+* https://git-scm.com/
+* https://maven.apache.org
diff --git a/content/doc/odata2/release.md b/content/doc/odata2/release.md
index 852feff..46858b1 100644
--- a/content/doc/odata2/release.md
+++ b/content/doc/odata2/release.md
@@ -7,13 +7,13 @@ Title: Release Documentation
### Introduction
This document describes the release guidelines for Apache Olingo. It heavily
refers
-to [standard Apache procedures to
release](http://maven.apache.org/developers/release/apache-release.html)
+to [standard Apache procedures to
release](https://maven.apache.org/developers/release/apache-release.html)
Maven based projects at Apache.
### Build Environments
-Apache Olingo is built and released with [Maven3](http://maven.apache.org) and
uses
-the <a
href="http://svn.apache.org/repos/asf/maven/pom/tags/apache-13/pom.xml";>Apache
POM version 13</a>.
+Apache Olingo is built and released with [Maven3](https://maven.apache.org)
and uses
+the <a
href="https://svn.apache.org/repos/asf/maven/pom/tags/apache-13/pom.xml";>Apache
POM version 13</a>.
### Release Artifacts
@@ -158,7 +158,7 @@ The release candidate artifacts:
- Maven artifacts will be staged on repository.apache.org. A new staging repo
is created per RC and will be communicated upon release.
- Distribution commodity packages are staged at
-http://people.apache.org/~[username]/olingo2/[version] (e.g.
http://people.apache.org/~mibo/olingo2/2.0.0-RC01)
+https://people.apache.org/~[username]/olingo2/[version] (e.g.
https://people.apache.org/~mibo/olingo2/2.0.0-RC01)
Once candidate artifacts are available, release manager kicks off the [VOTE
process][3].
@@ -171,7 +171,7 @@ If the release candidate gets approved, we can proceed to
release publishing.
This checklist helps verifying if a release candidate is valid:
-* Are all files on "http://people.apache.org/~[username]/olingo2/[version]";?
+* Are all files on "https://people.apache.org/~[username]/olingo2/[version]";?
* Check if md5, sha512 and asc files are filled correctly?
* Can the zip files be unpacked without issues?
* Execute a "mvn clean install -Pbuild.quality" on parent distribution. It
should work without issues.
@@ -193,9 +193,9 @@ made available
[here](https://repository.apache.org/index.html#nexus-search;gav~
- Publish final release Version to [Apache
Repository](https://repository.apache.org/)
- First publish via `mvn deploy -Papache-release` into the *Staging Area*
- From *Staging Area* close and release the staged Artifacts to finish
publishing
- - Afterwards the Maven artifacts are automatically synced to [Maven
Central](http://search.maven.org/#search|ga|1|org.apache.olingo).
+ - Afterwards the Maven artifacts are automatically synced to [Maven
Central](https://search.maven.org/#search|ga|1|org.apache.olingo).
- Release candidate commodity packages are synced (together with their
checksum and
-signatures) to [Apache Distributions](http://www.apache.org/dist/olingo/).
+signatures) to [Apache Distributions](https://www.apache.org/dist/olingo/).
- Release tag is renamed to final version.
- Release branch is created.
- Release is closed in Jira.
@@ -203,18 +203,18 @@ signatures) to [Apache
Distributions](http://www.apache.org/dist/olingo/).
### Maintain Release Distributions
-To maintain the released Distributions for the download pages following steps
are required (for more information see [Apache Distribution
Documentation](http://www.apache.org/dev/release-publishing.html#distribution_dist))
to upload the new distribution via SVN (`svn co
https://dist.apache.org/repos/dist/release/olingo`):
+To maintain the released Distributions for the download pages following steps
are required (for more information see [Apache Distribution
Documentation](https://www.apache.org/dev/release-publishing.html#distribution_dist))
to upload the new distribution via SVN (`svn co
https://dist.apache.org/repos/dist/release/olingo`):
- Check out latest SVN revision via `svn co
https://dist.apache.org/repos/dist/release/olingo`
- Change into the directory according to the released Olingo artifact (e.g.
`odata2`, `odata4`, ...)
- Create new directory according to release version (e.g `rel-x.x.x`) and
copy all distribution artifacts (includes *.zip*, *.asc*, *.md5*, *.sha512*).
- Add new directory (e.g. `svn add rel-x.x.x`) and do the commit (e.g `svn
ci -m "Added Olingo x.x.x release"`)
- - Afterwards do a cleanup for the old releases according to the Apache
Release Guidelines
[When](http://www.apache.org/dev/release.html#when-to-archive) and
[How](http://www.apache.org/dev/release.html#how-to-archive) to archive.
+ - Afterwards do a cleanup for the old releases according to the Apache
Release Guidelines
[When](https://www.apache.org/dev/release.html#when-to-archive) and
[How](https://www.apache.org/dev/release.html#how-to-archive) to archive.
### Maintain Version Section in DOAP File
-[http://olingo.apache.org/doap_Olingo.rdf][4]
+[https://olingo.apache.org/doap_Olingo.rdf][4]
Results are shown here:
@@ -230,7 +230,7 @@ Results are shown here:
[1]: /documentation.html
[2]: https://issues.apache.org/jira/browse/OLINGO/fixforversion/12324804
[4]: /doap_Olingo.rdf
- [5]: http://projects.apache.org/indexes/alpha.html#O
- [6]: http://www.apache.org/dev/release.html
- [7]: http://www.apache.org/dev/release-publishing.html
- [8]: http://www.apache.org/dev/publishing-maven-artifacts.html
+ [5]: https://projects.apache.org/indexes/alpha.html#O
+ [6]: https://www.apache.org/dev/release.html
+ [7]: https://www.apache.org/dev/release-publishing.html
+ [8]: https://www.apache.org/dev/publishing-maven-artifacts.html
diff --git a/content/doc/odata2/sample-setup.md
b/content/doc/odata2/sample-setup.md
index f53f36a..b8f11be 100644
--- a/content/doc/odata2/sample-setup.md
+++ b/content/doc/odata2/sample-setup.md
@@ -5,7 +5,7 @@ Title: Sample Project Setup
Olingo has prepared a very simple sample car service that can work as a
starting point for implementing a custom OData service.
This service consists of a very simple EDM with two entity sets that are cars
and manufactures and a memory based data provider that is a simple hash map.
Therefore the project implements a very basic single OData processor
supporting a minimal readonly scenario.
-If build with Maven the build result is a web application (`war` file) which
can be deployed to any JEE compliant web application server (e.g.
[Tomcat](http://tomcat.apache.org)).
+If build with Maven the build result is a web application (`war` file) which
can be deployed to any JEE compliant web application server (e.g.
[Tomcat](https://tomcat.apache.org)).
---
@@ -36,7 +36,7 @@ To generate the sample project for the `ODataService`
implementation with use o
-DarchetypeArtifactId=olingo-odata2-sample-cars-annotation-archetype \
-DarchetypeVersion=RELEASE
-If an archetype is not available via Maven standard configuration then an
additional parameter
`-DarchetypeRepository=http://repository.apache.org/snapshots` can solve the
issue.
+If an archetype is not available via Maven standard configuration then an
additional parameter
`-DarchetypeRepository=https://repository.apache.org/snapshots` can solve the
issue.
Based on the Olingo project template Maven will generate a new project with
the specified GAV*) coordinates: `com.sample:my-car-service:1.0.0-SNAPSHOT`.
GAV coordinates can be freely chosen during generation with the interactive
mode. To enable the interactive mode `-DinteractiveMode` must be set to true or
omitted (to use Maven default setting of `true`).
@@ -53,7 +53,7 @@ If a Apache Olingo dependency is not available via Maven
standard configuration
<repository>
<id>apache.central</id>
<name>Central Repository</name>
- <url>http://repo.maven.apache.org/maven2</url>
+ <url>https://repo.maven.apache.org/maven2</url>
</repository>
<repository>
diff --git a/content/doc/odata2/tomcat.md b/content/doc/odata2/tomcat.md
index b0990c9..ad0f12a 100644
--- a/content/doc/odata2/tomcat.md
+++ b/content/doc/odata2/tomcat.md
@@ -1,14 +1,14 @@
Title: Run with Tomcat
### Run with Tomcat
-Necessary steps to get your project run with
[Tomcat](http://tomcat.apache.org/index.html) (tested with version `7.0.32`).
+Necessary steps to get your project run with
[Tomcat](https://tomcat.apache.org/index.html) (tested with version `7.0.32`).
#### Required steps
- * Download Tomcat 7.0.x from [Tomcat
Downloads](http://tomcat.apache.org/download-70.cgi)
- * Install Tomcat as described in [Tomcat
Documentation](http://tomcat.apache.org/tomcat-7.0-doc/setup.html)
+ * Download Tomcat 7.0.x from [Tomcat
Downloads](https://tomcat.apache.org/download-70.cgi)
+ * Install Tomcat as described in [Tomcat
Documentation](https://tomcat.apache.org/tomcat-7.0-doc/setup.html)
* Start Tomcat e.g. via `$TOMCAT_HOME/bin/startup.sh` (Linux) or
`$TOMCAT_HOME/bin/startup.bat` (Windows)
* Build of OData Application
* Build your `WAR` file of your own project
* If you don't have a project the follow our sample project setup
[here](/doc/odata2/sample-setup.html)
* Deployment of the OData Application via simple copy of created `WAR` from
the web project `./target` folder (for the sample it is
`$ODATA_PROJECT_HOME/cars-web/target/olingo.odata2.sample.cars.web.war`) into
`$TOMCAT_HOME/webapps`
- * After successful deployment for the sample project just open following
link: http://localhost:8080/olingo.odata2.sample.cars.web to see the project
entry site.
\ No newline at end of file
+ * After successful deployment for the sample project just open following
link: http://localhost:8080/olingo.odata2.sample.cars.web to see the project
entry site.
diff --git a/content/doc/odata4/dependencies.md
b/content/doc/odata4/dependencies.md
index 65eefe4..2cda846 100644
--- a/content/doc/odata4/dependencies.md
+++ b/content/doc/odata4/dependencies.md
@@ -57,4 +57,4 @@ Whereas the variable `${olingo.version}` has to be replaced
with the concrete ve
See also:
* [Download Page](/doc/odata4/download.html)
-* [Maven Central](http://search.maven.org/#search|ga|1|org.apache.olingo)
+* [Maven Central](https://search.maven.org/#search|ga|1|org.apache.olingo)
diff --git a/content/doc/odata4/eclipse.md b/content/doc/odata4/eclipse.md
index 75aa307..d9bf171 100644
--- a/content/doc/odata4/eclipse.md
+++ b/content/doc/odata4/eclipse.md
@@ -4,7 +4,7 @@ Title: Eclipse
---
-[Eclipse](http://eclipse.org) (in version `Juno` and `Kepler`) is supported by
the project.
+[Eclipse](https://eclipse.org) (in version `Juno` and `Kepler`) is supported
by the project.
With the Maven project files can be generated with:
diff --git a/content/doc/odata4/index.md b/content/doc/odata4/index.md
index 37b3a8f..1f3e550 100644
--- a/content/doc/odata4/index.md
+++ b/content/doc/odata4/index.md
@@ -58,9 +58,9 @@ Title: Documentation
* [JPA Extension library for Olingo
V4](https://github.com/SAP/olingo-jpa-processor-v4)
* Series of blog articles which show a tutorial on how to use Olingo as
client library
* [Connection and Data-Exchange Java with Microsoft Dynamics with Olingo
V4.5.0](https://egmont-petersen.nl/mesmerize/java-html/connection-and-data-exchange-java-with-microsoft-dynamics/)
- * [Accessing data of OData v4 services with
Olingo](http://templth.wordpress.com/2014/12/03/accessing-odata-v4-service-with-olingo/)
- * [Manipulating data of OData v4 services with
Olingo](http://templth.wordpress.com/2014/12/05/manipulating-data-of-odata-v4-services-with-olingo/)
- * [Updating data links of OData v4 services with
Olingo](http://templth.wordpress.com/2014/12/08/updating-data-links-of-odata-v4-services-with-olingo/)
+ * [Accessing data of OData v4 services with
Olingo](https://templth.wordpress.com/2014/12/03/accessing-odata-v4-service-with-olingo/)
+ * [Manipulating data of OData v4 services with
Olingo](https://templth.wordpress.com/2014/12/05/manipulating-data-of-odata-v4-services-with-olingo/)
+ * [Updating data links of OData v4 services with
Olingo](https://templth.wordpress.com/2014/12/08/updating-data-links-of-odata-v4-services-with-olingo/)
* Blog articles which show different topics on how to use Olingo as server
library
* [Implementing an OData service with
Olingo](https://templth.wordpress.com/2015/04/27/implementing-an-odata-service-with-olingo/)
* [Handling OData queries with
ElasticSearch](https://templth.wordpress.com/2015/04/03/handling-odata-queries-with-elasticsearch/)
diff --git a/content/doc/odata4/maven.md b/content/doc/odata4/maven.md
index 02b005f..311549a 100644
--- a/content/doc/odata4/maven.md
+++ b/content/doc/odata4/maven.md
@@ -23,5 +23,5 @@ to run the build, execute JUnit tests and create all
artifacts.
Further information to Git and Maven is available here:
-* http://git-scm.com/
-* http://maven.apache.org
+* https://git-scm.com/
+* https://maven.apache.org
diff --git a/content/doc/odata4/release.md b/content/doc/odata4/release.md
index e97b2b2..e5daef3 100644
--- a/content/doc/odata4/release.md
+++ b/content/doc/odata4/release.md
@@ -7,13 +7,13 @@ Title: Apache Olingo Release Documentation
### Introduction
This document describes the release guidelines for Apache Olingo. It heavily
refers
-to [standard Apache procedures to
release](http://maven.apache.org/developers/release/apache-release.html)
+to [standard Apache procedures to
release](https://maven.apache.org/developers/release/apache-release.html)
Maven based projects at Apache.
### Build Environments
-Apache Olingo is built and released with [Maven 3](http://maven.apache.org)
and uses
-the <a
href="http://svn.apache.org/repos/asf/maven/pom/tags/apache-16/pom.xml";>Apache
POM version 16</a>.
+Apache Olingo is built and released with [Maven 3](https://maven.apache.org)
and uses
+the <a
href="https://svn.apache.org/repos/asf/maven/pom/tags/apache-16/pom.xml";>Apache
POM version 16</a>.
### Release Artifacts
@@ -148,7 +148,7 @@ The release candidate artifacts:
- Maven artifacts will be staged on repository.apache.org. A new staging repo
is created per RC and will be communicated upon release.
- Distribution commodity packages are staged at
-http://people.apache.org/~[username]/olingo2/[version] (e.g.
http://people.apache.org/~mibo/olingo4/4.0.0-RC01)
+https://people.apache.org/~[username]/olingo2/[version] (e.g.
https://people.apache.org/~mibo/olingo4/4.0.0-RC01)
Once candidate artifacts are available, release manager kicks off the [VOTE
process][3].
@@ -161,7 +161,7 @@ If the release candidate gets approved, we can proceed to
release publishing.
This checklist helps verifying if a release candidate is valid:
-* Are all files on "http://people.apache.org/~[username]/olingo4/[version]";?
+* Are all files on "https://people.apache.org/~[username]/olingo4/[version]";?
* Check if md5, sha512 and asc files are filled correctly?
* Can the zip files be unpacked without issues?
* Execute a "mvn clean install -Pbuild.quality" on parent distribution. It
should work without issues.
@@ -183,9 +183,9 @@ made available
[here](https://repository.apache.org/index.html#nexus-search;gav~
- Publish final release Version to [Apache
Repository](https://repository.apache.org/)
- First publish via `mvn deploy -Papache-release` into the *Staging Area*
- From *Staging Area* close and release the staged Artifacts to finish
publishing
- - Afterwards the Maven artifacts are automatically synced to [Maven
Central](http://search.maven.org/#search|ga|1|org.apache.olingo).
+ - Afterwards the Maven artifacts are automatically synced to [Maven
Central](https://search.maven.org/#search|ga|1|org.apache.olingo).
- Release candidate commodity packages are synced (together with their
checksum and
-signatures) to [Apache Distributions](http://www.apache.org/dist/olingo/).
+signatures) to [Apache Distributions](https://www.apache.org/dist/olingo/).
- Release tag is renamed to final version.
- Release branch is created.
- Release is closed in Jira.
@@ -193,18 +193,18 @@ signatures) to [Apache
Distributions](http://www.apache.org/dist/olingo/).
### Maintain Release Distributions
-To maintain the released Distributions for the download pages following steps
are required (for more information see [Apache Distribution
Documentation](http://www.apache.org/dev/release-publishing.html#distribution_dist))
to upload the new distribution via SVN (`svn co
https://dist.apache.org/repos/dist/release/olingo`):
+To maintain the released Distributions for the download pages following steps
are required (for more information see [Apache Distribution
Documentation](https://www.apache.org/dev/release-publishing.html#distribution_dist))
to upload the new distribution via SVN (`svn co
https://dist.apache.org/repos/dist/release/olingo`):
- Check out latest SVN revision via `svn co
https://dist.apache.org/repos/dist/release/olingo`
- Change into the directory according to the released Olingo artifact (e.g.
`odata2`, `odata4`, ...)
- Create new directory according to release version (e.g `rel-x.x.x`) and
copy all distribution artifacts (includes *.zip*, *.asc*, *.md5*, *.sha512*).
- Add new directory (e.g. `svn add rel-x.x.x`) and do the commit (e.g `svn
ci -m "Added Olingo x.x.x release"`)
- - Afterwards do a cleanup for the old releases according to the Apache
Release Guidelines
[When](http://www.apache.org/dev/release.html#when-to-archive) and
[How](http://www.apache.org/dev/release.html#how-to-archive) to archive.
+ - Afterwards do a cleanup for the old releases according to the Apache
Release Guidelines
[When](https://www.apache.org/dev/release.html#when-to-archive) and
[How](https://www.apache.org/dev/release.html#how-to-archive) to archive.
### Maintain Version Section in DOAP File
-[http://olingo.apache.org/doap_Olingo.rdf][4]
+[https://olingo.apache.org/doap_Olingo.rdf][4]
Results are shown here:
@@ -220,7 +220,7 @@ Results are shown here:
[1]: /documentation.html
[2]: https://issues.apache.org/jira/browse/OLINGO/fixforversion/12324804
[4]: /doap_Olingo.rdf
- [5]: http://projects.apache.org/indexes/alpha.html#O
- [6]: http://www.apache.org/dev/release.html
- [7]: http://www.apache.org/dev/release-publishing.html
- [8]: http://www.apache.org/dev/publishing-maven-artifacts.html
+ [5]: https://projects.apache.org/indexes/alpha.html#O
+ [6]: https://www.apache.org/dev/release.html
+ [7]: https://www.apache.org/dev/release-publishing.html
+ [8]: https://www.apache.org/dev/publishing-maven-artifacts.html
diff --git a/content/doc/odata4/sample-setup.md
b/content/doc/odata4/sample-setup.md
index 7d7f457..96a5e15 100644
--- a/content/doc/odata4/sample-setup.md
+++ b/content/doc/odata4/sample-setup.md
@@ -5,7 +5,7 @@ Title: Sample Project Setup
Olingo has prepared a very simple sample car service that can work as a
starting point for implementing a custom OData service.
This service consists of a very simple EDM with two entity sets that are cars
and manufactures and a memory based data provider that is a simple hash map.
Therefore the project implements a very basic single OData processor
supporting a minimal readonly scenario.
-If build with Maven the build result is a web application (`war` file) which
can be deployed to any JEE compliant web application server (e.g.
[Tomcat](http://tomcat.apache.org)).
+If build with Maven the build result is a web application (`war` file) which
can be deployed to any JEE compliant web application server (e.g.
[Tomcat](https://tomcat.apache.org)).
---
diff --git a/content/doc/odata4/tomcat.md b/content/doc/odata4/tomcat.md
index b4af032..1acd73b 100644
--- a/content/doc/odata4/tomcat.md
+++ b/content/doc/odata4/tomcat.md
@@ -1,11 +1,11 @@
Title: Run with Tomcat
### Run with Tomcat
-Necessary steps to get your project run with
[Tomcat](http://tomcat.apache.org/index.html) (tested with version `7.0.32`).
+Necessary steps to get your project run with
[Tomcat](https://tomcat.apache.org/index.html) (tested with version `7.0.32`).
#### Required steps
- * Download Tomcat 7.0.x from [Tomcat
Downloads](http://tomcat.apache.org/download-70.cgi)
- * Install Tomcat as described in [Tomcat
Documentation](http://tomcat.apache.org/tomcat-7.0-doc/setup.html)
+ * Download Tomcat 7.0.x from [Tomcat
Downloads](https://tomcat.apache.org/download-70.cgi)
+ * Install Tomcat as described in [Tomcat
Documentation](https://tomcat.apache.org/tomcat-7.0-doc/setup.html)
* Start Tomcat e.g. via `$TOMCAT_HOME/bin/startup.sh` (Linux) or
`$TOMCAT_HOME/bin/startup.bat` (Windows)
* Build of OData Application
* Build your `WAR` file of your own project
diff --git a/content/download.md b/content/download.md
index f01f88d..98314f4 100644
--- a/content/download.md
+++ b/content/download.md
@@ -9,7 +9,7 @@ implementing [OData V2][1] protocol clients or servers.
[Download options for latest release 2.0.3
(2015-03-05)](/doc/odata2/download.html)
##### Maven
-Apache Olingo OData2 artifacts are available at [Maven
Central](http://search.maven.org/#search|ga|1|org.apache.olingo). For POM
dependencies see [here](/doc/odata2/maven.html).
+Apache Olingo OData2 artifacts are available at [Maven
Central](https://search.maven.org/#search|ga|1|org.apache.olingo). For POM
dependencies see [here](/doc/odata2/maven.html).
### Download Apache Olingo OData 4.0 Java Library
@@ -19,7 +19,7 @@ implementing [OData V4][1] protocol clients (Android/Java) or
servers.
[Download options for latest release 4.0.0-beta-02
(2015-01-29)](/doc/odata4/download.html)
##### Maven
-Apache Olingo OData4 artifacts are available at [Maven
Central](http://search.maven.org/#search|ga|1|org.apache.olingo). For POM
dependencies see [here](/doc/odata4/maven.html).
+Apache Olingo OData4 artifacts are available at [Maven
Central](https://search.maven.org/#search|ga|1|org.apache.olingo). For POM
dependencies see [here](/doc/odata4/maven.html).
### Download Olingo OData Client for JavaScript Library
The Olingo OData Client for JavaScript (odatajs) is a library written in
JavaScript that enables browser based frontend applications to easily use the
OData protocol for communication with application servers.
@@ -27,4 +27,4 @@ The Olingo OData Client for JavaScript (odatajs) is a library
written in JavaScr
[Download options for latest release 4.0.0-beta-01
(2014-09-15)](/doc/javascript/download.html)
- [1]: http://odata.org
+ [1]: https://www.odata.org
diff --git a/content/index.md b/content/index.md
index f09508a..8c81bad 100644
--- a/content/index.md
+++ b/content/index.md
@@ -2,7 +2,7 @@ Title: Apache Olingo
<div class="jumbotron">
<h1>
-Apache Olingo™ <a href="http://odata.org/";><img
src="/img/odata/ODataLogo-48.png" alt="OlingoLogo"></a>
+Apache Olingo™ <a href="https://www.odata.org/";><img
src="/img/odata/ODataLogo-48.png" alt="OlingoLogo"></a>
</h1>
<h3>
What is the Apache Olingo Project?
diff --git a/content/support.md b/content/support.md
index f028e39..3265ddb 100644
--- a/content/support.md
+++ b/content/support.md
@@ -6,13 +6,13 @@ Title: Support
### Mailing Lists
-Apache Olingo has following public mailing list, archived by
[Markmail](http://markmail.org).
+Apache Olingo has following public mailing list, archived by
[Markmail](https://markmail.org).
Mailing list | Email | ASF Archives | Markmail Archives | Subscribe
-------------|-------|--------------|-------------------|----------
-Users and Stakeholders | [user@<wbr />olingo.<wbr />apache.<wbr
/>org](mailto:[email protected]) |
[archive](http://mail-archives.apache.org/mod_mbox/olingo-user/) |
[archive](http://markmail.org/search/list:org.apache.olingo.user) |
[user-subscribe@<wbr />olingo.<wbr />apache.<wbr
/>org](mailto:[email protected])
-Contributors | [dev@<wbr />olingo.<wbr />apache.<wbr
/>org](mailto:[email protected]) |
[archive](http://mail-archives.apache.org/mod_mbox/olingo-dev/) |
[archive](http://markmail.org/search/list:org.apache.olingo.dev) |
[dev-subscribe@<wbr />olingo.<wbr />apache.<wbr
/>org](mailto:[email protected])
+Users and Stakeholders | [user@<wbr />olingo.<wbr />apache.<wbr
/>org](mailto:[email protected]) |
[archive](https://mail-archives.apache.org/mod_mbox/olingo-user/) |
[archive](https://markmail.org/search/list:org.apache.olingo.user) |
[user-subscribe@<wbr />olingo.<wbr />apache.<wbr
/>org](mailto:[email protected])
+Contributors | [dev@<wbr />olingo.<wbr />apache.<wbr
/>org](mailto:[email protected]) |
[archive](https://mail-archives.apache.org/mod_mbox/olingo-dev/) |
[archive](https://markmail.org/search/list:org.apache.olingo.dev) |
[dev-subscribe@<wbr />olingo.<wbr />apache.<wbr
/>org](mailto:[email protected])
Read the archives first in case your question has already been answered. If
not, then subscribe to the appropriate list and post your question
(subscription is required to send a mail to the related list).
@@ -31,5 +31,5 @@ To unsubscribe from our lists just send a mail to
<list-name>-unsubscribe@
- [JIRA](https://issues.apache.org/jira/browse/OLINGO)
- [CI Builds](https://builds.apache.org/view/M-R/view/Olingo/)
- [Apache Analyse
(SonarQube)](https://analysis.apache.org/dashboard/index?id=org.apache.olingo%3Aodata-parent)
-- [Committers and PMC of Apache
Olingo](http://people.apache.org/committers-by-project.html#olingo)
+- [Committers and PMC of Apache
Olingo](https://people.apache.org/committers-by-project.html#olingo)
diff --git a/content/verification.md b/content/verification.md
index 7aeb753..f01d0e8 100644
--- a/content/verification.md
+++ b/content/verification.md
@@ -6,14 +6,14 @@ Title: Verification
It is essential that you verify the integrity of the downloaded
files using the PGP signatures. Please read
-[Verifying Apache HTTP Server
Releases](http://httpd.apache.org/dev/verification.html)
+[Verifying Apache HTTP Server
Releases](https://httpd.apache.org/dev/verification.html)
for more information on why you should verify our releases.
The PGP signatures can be verified using PGP or GPG. First download
-the [KEYS](http://www.apache.org/dist/olingo/KEYS) file as well
+the [KEYS](https://www.apache.org/dist/olingo/KEYS) file as well
as the .asc signature files for the relevant release packages. Make sure
you get these files from the
-[main distribution directory](http://www.apache.org/dist/olingo/),
+[main distribution directory](https://www.apache.org/dist/olingo/),
rather than from a mirror. Then verify the signatures using
```sh
@@ -33,4 +33,4 @@ or
```sh
% gpg --import KEYS
% gpg --verify <file>.asc
-```
\ No newline at end of file
+```
diff --git a/theme/apache/templates/base.html b/theme/apache/templates/base.html
index 1b724f0..9697817 100644
--- a/theme/apache/templates/base.html
+++ b/theme/apache/templates/base.html
@@ -66,17 +66,17 @@ under the License.
<li class="dropdown">
<a href="#" class="dropdown-toggle"
data-toggle="dropdown">ASF <b class="caret"></b></a>
<ul class="dropdown-menu">
- <li><a href="http://www.apache.org/foundation/";>ASF
Home</a></li>
- <li><a
href="http://projects.apache.org/";>Projects</a></li>
- <li><a href="http://people.apache.org/";>People</a></li>
- <li><a
href="http://www.apache.org/foundation/getinvolved.html";>Get Involved</a></li>
- <li><a
href="http://www.apache.org/dyn/closer.cgi";>Download</a></li>
- <li><a
href="http://www.apache.org/security/";>Security</a></li>
- <li><a
href="http://www.apache.org/foundation/sponsorship.html";>Support Apache</a></li>
+ <li><a href="https://www.apache.org/foundation/";>ASF
Home</a></li>
+ <li><a
href="https://projects.apache.org/";>Projects</a></li>
+ <li><a href="https://people.apache.org/";>People</a></li>
+ <li><a
href="https://www.apache.org/foundation/getinvolved.html";>Get Involved</a></li>
+ <li><a
href="https://www.apache.org/dyn/closer.cgi";>Download</a></li>
+ <li><a
href="https://www.apache.org/security/";>Security</a></li>
+ <li><a
href="https://www.apache.org/foundation/sponsorship.html";>Support
Apache</a></li>
</ul>
</li>
- <li><a href="http://www.apache.org/licenses/";>License</a></li>
+ <li><a href="https://www.apache.org/licenses/";>License</a></li>
<li class="dropdown">
<a href="#" class="dropdown-toggle"
data-toggle="dropdown">Download <b class="caret"></b></a>
@@ -100,7 +100,7 @@ under the License.
</ul>
- <a class="navbar-right"
href="http://www.apache.org/foundation/"; target="_blank">
+ <a class="navbar-right"
href="https://www.apache.org/foundation/"; target="_blank">
<img class="navbar-right" height="50px" src="/img/asf_logo_url.svg"
alt="Apache Software Foundation">
</a>
