Skip to content

Commit de39d8a

Browse files
Pre Release Clean Up
1 parent 8e1f093 commit de39d8a

File tree

4 files changed

+20
-30
lines changed

4 files changed

+20
-30
lines changed

BUILDANDTEST.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,17 @@
11
# _Build and testing instructions_
22

3+
## Setup
4+
5+
1. Clone the repo to your local directory
6+
2. Change to the installation directory
7+
38
## To build the generator and run the JUnit tests
49

510
```sh
611
mvn clean install
712
```
813

9-
There are two types of JUnit tests to confirm that generated code matches expectations.
10-
11-
1. In memory string comparisons of generated Python to expected results.
12-
2. Generated Python written to the file system (see the target directory) compared to expected results read from the file system (see the directory test/compare_generated_syntax/expected).
14+
The JUnit tests conduct string comparisons of Python generated from Rune samples expected results.
1315

1416
All tests should pass.
1517

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
This document describes the contribution process and governance policies of the FINOS {project name} project. The project is also governed by the [Linux Foundation Antitrust Policy](https://www.linuxfoundation.org/antitrust-policy/), and the FINOS [IP Policy]( https://community.finos.org/governance-docs/IP-policy.pdf), [Code of Conduct](https://community.finos.org/docs/governance/code-of-conduct), [Collaborative Principles](https://community.finos.org/docs/governance/collaborative-principles/), and [Meeting Procedures](https://community.finos.org/docs/governance/meeting-procedures/).
44

55
## Contribution Process
6-
x
6+
77
Before making a contribution, please take the following steps:
88
1. Check whether there's already an open issue related to your proposed contribution. If there is, join the discussion and propose your contribution there.
99
2. If there isn't already a relevant issue, create one, describing your contribution and the problem you're trying to solve.

README.md

Lines changed: 11 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -9,39 +9,27 @@ The Python package requires Python version 3.11+.
99
## Repository Organization
1010

1111
- `README.md` - this file, for documentation purposes
12+
- `BUILDANDTEST.md` - instructions on building and testing the repo
13+
- `RELEASE.md` - information about the current release
1214
- `src/main` - Java/Xtend code to generate Python from Rune
1315
- `src/test` - Java/Xtend code to run JUnit tests on the code generation process
1416
- `build` - configuration scripts to setup and tear down the Python unit testing environment
1517
- `build/build_cdm.sh` - used to create a Python package from code generated using CDM Rune definitions
1618
- `test` - Python unit tests and scripts to run the tests
1719

18-
## Prerequisites
19-
20-
[Eclipse 2021 (JSEE) + xtend support Eclipse IDE for Java and DSL Developers](https://www.eclipse.org/downloads/packages/release/2021-12/r/eclipse-ide-java-and-dsl-developers)
21-
22-
[Git](https://git-scm.com/)
20+
## Installation Steps
21+
Detailed build and testing instructions can be found in [BUILDANDTEST.md](./BUILDANDTEST.md)
2322

24-
[Maven](http://maven.apache.org/)
23+
A quick overview follows:
2524

26-
## Installation Steps
27-
1. Create a directory structure hereafter referred to as [CODEGEN]
28-
```
29-
mkdir -p [CODEGEN]
30-
```
31-
2. Fork and clone the generator
32-
Fork a copy from `https://github.com/REGnosys/rune-python-generator` ([MYREPO])
33-
```
34-
cd [CODEGEN]
35-
git clone https://github.com/[MYREPO]/rune-python-generator.git
36-
```
37-
3. Build and test using Maven
25+
1. Make a local copy of this repo
26+
2. Build and test using Maven
3827
```
3928
cd rune-python-generator
4029
mvn -s clean install
4130
```
4231
All the tests should pass.
4332

44-
More build and testing instructions can be found in [BUILDANDTEST.md](./BUILDANDTEST.md)
4533

4634
## Contributing
4735
For any questions, bugs or feature requests please open an [issue](https://github.com/regnosys/rune-python-generator/issues)
@@ -61,14 +49,14 @@ Use this script to generated the Python version of CDM
6149
```sh
6250
build/build_cdm.sh
6351
```
64-
The script will use the CDM from the master branch of the [FINOS Repo](https://github.com/finos/common-domain-model) and generate a wheel in the project directory `target/python-cdm`
52+
The script will use the CDM from the branch specified in the file (E.G. master) of the [FINOS Repo](https://github.com/finos/common-domain-model) and generate a wheel in the project directory `target/python-cdm`
6553

6654
To use a different version of CDM, update CDM_VERSION in the script.
6755

6856
## Contributors
69-
- [CloudRisk](https://www.cloudrisk.uk)
70-
- [FT Advisory LLC](https://www.ftadvisory.co)
71-
- [TradeHeader SL](https://www.tradeheader.com)
57+
- [CLOUDRISK Limited](https://www.cloudrisk.uk), email: [email protected]
58+
- [FT Advisory LLC](https://www.ftadvisory.co), email: [email protected]
59+
- [TradeHeader SL](https://www.tradeheader.com), email: [email protected]
7260

7361
## Governance
7462

build/get_cdm.sh

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,8 @@ rm -rf common-domain-model
1919
mkdir common-domain-model
2020
cd common-domain-model
2121
echo "***** pull CDM rosetta definitions"
22-
CDM_VERSION="5.22.1"
23-
# CDM_VERSION="master"
22+
# CDM_VERSION="5.22.1"
23+
CDM_VERSION="master"
2424
git init
2525
git config core.sparseCheckout true
2626
echo "rosetta-source/src/main/rosetta" >> .git/info/sparse-checkout

0 commit comments

Comments
 (0)