Architectural Decision Log

This lists the architectural decisions for Eclipse Winery.

  • ADR-0000 - Use Markdown Architectural Decision Records

  • ADR-0001 - Use filesystem as backend

  • ADR-0002 - File system folder structure using type-namespace-id structure

  • ADR-0003 - Double Encoded URLs

  • ADR-0004 - OAuth with GitHub

  • ADR-0005 - XML editor does not enforce validation

  • ADR-0006 - Wrap properties in TOSCA properties element

  • ADR-0007 - Custom URI for lifecycle interface

  • ADR-0008 - No support for local git source clones

  • ADR-0009 - Manual serialization of SnakeYAML

  • ADR-0010 - TOSCA YAML deserialization using SnakeYAML

  • ADR-0011 - Use Builder Pattern for Model Classes

  • ADR-0012 - Provide Support for Custom Key-Value Properties

  • ADR-0013 - Routes in the Repository Angular App

  • ADR-0014 - Use Eclipse Orion as Editor

  • ADR-0015 - Offer copying files from the source to the files folder

  • ADR-0016 - Reflection test for TOSCA YAML builder

  • ADR-0017 - Modify JAX-B generated classes

  • ADR-0018 - Version Identifier in a Debian-like Form

  • ADR-0019 - Versions of TOSCA elements in the name

  • ADR-0020 - TOSCA Definitions contain excaly one element

  • ADR-0021 - Use logback for logging

  • ADR-0022 - tosca.model is more relaxed than the XSD

  • ADR-0023 - Use Maven as build tool

  • ADR-0024 - Use TravisCI for Continuous Integration

  • ADR-0025 - Use same logback-test.xml for each sub project

  • ADR-0026 - Store LICENSE and README.md in respective entity’s root folder in a CSAR

  • ADR-0027 - Use dasherization for filenames

  • ADR-0028 - Use hardcoded namespaces for threat modeling

  • ADR-0029 - IPSec Algorithm Implementation

  • ADR-0030 - Support of multiple repositories

  • ADR-0031 - Reuse the pattern refinement implementation for pattern detection

The template.md contains the MADR template. More information on MADR is available at https://adr.github.io/madr/.