CySeC bridge

The CySeC briddge provides compile time dependencies for coaches running on the CySeC platform.

License

License

Categories

Categories

ORM Data
GroupId

GroupId

eu.smesec.platform
ArtifactId

ArtifactId

cysec_bridge
Last Version

Last Version

0.2.0
Release Date

Release Date

Type

Type

jar
Description

Description

CySeC bridge
The CySeC briddge provides compile time dependencies for coaches running on the CySeC 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 cysec_bridge

How to add to project

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

Dependencies

compile (3)

Group / Artifact Type Version
org.jvnet.jaxb2_commons : jaxb2-basics-runtime jar 0.11.1
javax.xml.bind : jaxb-api jar 2.3.0
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

There are no modules declared in this project.

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