From ad81d2bf34f67a4da1a126a14b1cd61858d9b6e6 Mon Sep 17 00:00:00 2001 From: Malo <mtc@kereval.com> Date: Tue, 13 Apr 2021 15:42:43 +0200 Subject: [PATCH] from gforge to gitlab URLs --- Gazelle-FHIR-Validator/installation.md | 4 ++-- Gazelle-FHIR-Validator/user.md | 2 +- Order-Manager/installation.md | 6 ++++-- Patient-Manager/installation.md | 6 +++++- SVS-Simulator/installation.md | 6 ++++-- 5 files changed, 16 insertions(+), 8 deletions(-) diff --git a/Gazelle-FHIR-Validator/installation.md b/Gazelle-FHIR-Validator/installation.md index 756a313..a02eb81 100644 --- a/Gazelle-FHIR-Validator/installation.md +++ b/Gazelle-FHIR-Validator/installation.md @@ -70,7 +70,7 @@ A project you can use to deploy a FHIR server using HAPI FHIR JPA validation wit ## IHE Structure Definitions -SQL script files available in the project directory imports entries to use the structure definitions and value sets defined by IHE. In order to use them, you can checkout the content of [fhir-structure-definitions](https://scm.gforge.inria.fr/anonscm/svn/gazelle/fhir-structure-definitions/trunk/) directory from Inria's forge into /opt/fhirvalidator folder. It is the default location used by the tool. This can however be changed by updating the path to each custom structure definition in the database. +SQL script files available in the project directory imports entries to use the structure definitions and value sets defined by IHE. In order to use them, you can checkout the content of [fhir-structure-definitions](https://gitlab.inria.fr/gazelle/test-content/fhir-conformance-resources) directory from Inria's forge into /opt/fhirvalidator folder. It is the default location used by the tool. This can however be changed by updating the path to each custom structure definition in the database. ## Accesses @@ -189,4 +189,4 @@ For each parameter, the following attributes are used: The name of the validators uses the following pattern: [TRANSACTION-KEYWORD] Message name where: * TRANSACTION-KEYWORD is the keyword of the transaction which is checked using this validator -* Message name is the name of the message as defined in the technical framework \ No newline at end of file +* Message name is the name of the message as defined in the technical framework diff --git a/Gazelle-FHIR-Validator/user.md b/Gazelle-FHIR-Validator/user.md index 6197c73..d92bb88 100755 --- a/Gazelle-FHIR-Validator/user.md +++ b/Gazelle-FHIR-Validator/user.md @@ -26,7 +26,7 @@ The validation service is offered as a SOAP API. You can validate your messages # Using the validation service -A SoapUI project is available in the directory of the tool on Inria's forge. [SoapUI](https://scm.gforge.inria.fr/svn/gazelle/Maven/FhirValidator/trunk/FhirValidator-ear/src/main/resources/) +A SoapUI project is available in the directory of the tool on Inria's forge. [SoapUI](https://gitlab.inria.fr/gazelle/validator/FhirValidator/-/tree/master/FhirValidator-ear/src/main/resources/soapui) # Graphical user interface diff --git a/Order-Manager/installation.md b/Order-Manager/installation.md index db91a4d..6f148b1 100755 --- a/Order-Manager/installation.md +++ b/Order-Manager/installation.md @@ -20,10 +20,12 @@ To get the artifact on Nexus browse: [*https://gazelle.ihe.net/nexus/index.html\ If you rather want to build the project by yourself, you must checkout the latest tag and package it. You may want to create a new Maven profile to customize your build. -Checkout the latest tag available on Inria’s forge: +Checkout the latest tag available on Inria’s gitlab: ```bash -svn co svn checkout https://scm.gforge.inria.fr/anonscm/svn/gazelle/Maven/simulators/OrderManager/tags/OrderManager-versionName +git clone https://gitlab.inria.fr/gazelle/applications/test-execution/simulator/order-manager.git +cd order-manager +git checkout tags/OrderManager-<version> ``` 1. \[Optional\] Edit the pom.xml file and create a new profile diff --git a/Patient-Manager/installation.md b/Patient-Manager/installation.md index 464f0f3..9dacd5c 100755 --- a/Patient-Manager/installation.md +++ b/Patient-Manager/installation.md @@ -27,7 +27,11 @@ If you have your own CAS service, you need to package your own version of the to 1. Checkout the last tagged version available in Gazelle sources repository ($versionName will depend of the release you want to checkout) - `svn co https://scm.gforge.inria.fr/svn/gazelle/Maven/simulators/PAMSimulator/tags/PAMSimulator-$versionName` + ```bash + git clone https://gitlab.inria.fr/gazelle/applications/test-execution/simulator/Patient-Manager.git + cd PAMSimulator + git checkout tags/PAMSimulator-$versionName + ``` 4. Package the Patient Manager project. Go to the PAMSimulator folder then apply the following command line diff --git a/SVS-Simulator/installation.md b/SVS-Simulator/installation.md index 1ca0c1d..6b45e9f 100755 --- a/SVS-Simulator/installation.md +++ b/SVS-Simulator/installation.md @@ -25,8 +25,10 @@ If you rather want to build the project by yourself, you must checkout the lates 1- Checkout the latest tag available on Inria’s forge: -``` -$>svn co https://scm.gforge.inria.fr/svn/gazelle/Maven/simulators/SVSSimulator/tags/SVSSimulator-$versionName +```bash +git clone https://gitlab.inria.fr/gazelle/applications/test-execution/simulator/svs-simulator.git +cd svs-simulator +git checkout tag/SVSSimulator-<version> ``` 2- \[Optional\] Edit the pom.xml file and create a new profile -- GitLab