JarCasting
JarCasting JarCasting

CySeC

The CySeC coach runtime platform.

Лицензия

Лицензия
Категории

Категории

ORM Данные
Группа

Группа

eu.smesec.platform
Идентификатор

Идентификатор

coach_platform
Последняя версия

Последняя версия

0.2.0
Дата

Дата
Тип

Тип

pom
Описание

Описание

CySeC
The CySeC coach runtime platform.
Ссылка на сайт

Ссылка на сайт

http://cysec.cyberlab.fhnw.ch/
Система контроля версий

Система контроля версий

https://github.com/cysec-platform/cysec-platform/tree/master

Скачать coach_platform

Имя Файла Размер
coach_platform-0.2.0.pom 5 KB
Обзор

Как подключить последнюю версию

<!-- https://jarcasting.com/artifacts/eu.smesec.platform/coach_platform/ -->
<dependency>
    <groupId>eu.smesec.platform</groupId>
    <artifactId>coach_platform</artifactId>
    <version>0.2.0</version>
    <type>pom</type>
</dependency>
// https://jarcasting.com/artifacts/eu.smesec.platform/coach_platform/
implementation 'eu.smesec.platform:coach_platform:0.2.0'
// https://jarcasting.com/artifacts/eu.smesec.platform/coach_platform/
implementation ("eu.smesec.platform:coach_platform:0.2.0")
'eu.smesec.platform:coach_platform:pom:0.2.0'
<dependency org="eu.smesec.platform" name="coach_platform" rev="0.2.0">
  <artifact name="coach_platform" type="pom" />
</dependency>
@Grapes(
@Grab(group='eu.smesec.platform', module='coach_platform', version='0.2.0')
)
libraryDependencies += "eu.smesec.platform" % "coach_platform" % "0.2.0"
[eu.smesec.platform/coach_platform "0.2.0"]

Зависимости

compile (1)

Идентификатор библиотеки Тип Версия
org.mockito : mockito-core jar 2.23.4

test (2)

Идентификатор библиотеки Тип Версия
junit : junit jar 4.13.1
org.hamcrest : hamcrest-core jar 1.3

Модули Проекта

  • cysec_bridge
  • cysec_backend

CySeC main repo

This is the main repo for the SMESEC project.

Development dependencies

  • Java 8
  • Tomcat 9
  • Maven

Branching

Branching was loosely based on the Gitflow branching model, which should be adhered to more rigidly as the project moves to a Beta phase.

The Gitflow workflow is described f.ex. here.

This model should make for stable release branches and avoid any merge conflict issues.

The "master" branch is for stable releases and should rarely see commits.

The "dev" branch is for testing and should see regular changes, with additional commits as releases approach.

Feature and bugfix branches are based on "dev" unless the bugfix is specifically meant to be applied to a specific already-released version.

License

See MIT license

Версии библиотеки

Версия
0.2.0