Architectural decisions

List of important architectural decisions. For each decision the following attributes should be given:

• Title
• Date when the decision was made
• Full Description (with excerpt)
• Environmental constraints
• Pros
• Cons
• Who was involved
• References to mailing list threads

While all of the above information is also present on the list it is often quite confusing to read through long threads. Often people also change their opinion so reading one mail on the list can even lead in the wrong direction. Using this documentation we hope to avoid having the same discussions over and over again. At the same time the idea is to revisit decisions in some interval and either aprove they are still valid or change them.

Architectural decisions in chronological order

• 2010-09-10 Inline jline and jansi into console project
• 2011-10-26 Karaf module structure is feature based — From Karaf 3 on the module structure is layed out by features on the first level. A new module core is introduced that contains shared services for the feature.