- Maven - version
3.5+ - Java Development Kit 17+
To install the project locally:
mvn clean install -Dgpg.skip=trueTo build and test the project:
mvn clean packagenote: We recommend that you execute this command before committing changes in the git repository.
To build the project but skip testing:
mvn clean package -DskipTests=trueTo obtain the dependency trees that can help to resolve issues with conflict in dependencies
mvn dependency:treeTo increment versions in all submodules:
mvn versions:set -DnewVersion=your_new_versionnote: Incrementing the version is recommended for each PR with siembol java code change. Use version name with
SNAPSHOTif you are not preparing a release version.
The current NodeJS version used can be found in the github actions pipeline here.
The current Angular version can be found in the package.json file.
To build the project:
npm run buildThe build artifacts will be stored in the dist/ directory. Use the -prod flag for a production build.
To start a development server, run:
npm run startNavigate to http://localhost:4200 to view the UI.
The app will automatically reload if you change any of the source files.
to execute the unit tests via Karma, run:
npm run testTo lint all files:
npm run lintTo lint all files and fix linting errors:
npm run lint-fixTo change the dependencies listed in package.json, run:
npm installAlways update and commit dependencies in the package lock file
note: Please compress the package-lock.json file into one line so it does not affect the contributor statistics. Powershell example:
Get-Content package-lock.json | ConvertFrom-Json | ConvertTo-Json -compress -Depth 10 | Out-File package-lock2.json -Encoding ascii ; rm package-lock.json ; mv package-lock2.json package-lock.jsonThe config editor's UI version should be increased after each code change in package.json.