JarCasting
JarCasting JarCasting

CySeC

The CySeC coach runtime platform.

License

License
Categories

Categories

ORM Data
GroupId

GroupId

eu.smesec.platform
ArtifactId

ArtifactId

coach_platform
Last Version

Last Version

0.2.0
Release Date

Release Date
Type

Type

pom
Description

Description

CySeC
The CySeC coach runtime platform.
Project URL

Project URL

http://cysec.cyberlab.fhnw.ch/
Source Code Management

Source Code Management

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

Download coach_platform

Filename Size
coach_platform-0.2.0.pom 5 KB
Browse

How to add to project

<!-- 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"]

Dependencies

compile (1)

Group / Artifact Type Version
org.mockito : mockito-core jar 2.23.4

test (2)

Group / Artifact Type Version
junit : junit jar 4.13.1
org.hamcrest : hamcrest-core jar 1.3

Project Modules

  • 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

Versions

Version
0.2.0