[SMX4-883] Alter packaging options to better reflect common use cases

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.3.0
• Fix Version/s: 4.4.0
• Assignee: Ioannis Canellos
• Reporter: Gert Vanthienen
• Created: 22/Jul/11 08:18
• Updated: 26/Oct/11 14:08
• Resolved: 26/Oct/11 14:08

Description

Currently, we have one kind of assembly, which is mostly geared towards our existing JBI user base. We would like this to evolve into 3 distinct packaging options:

• apache-servicemix-4.x.0 : our recommended getting started platform, Karaf + Camel/ActiveMQ (+ CXF?)
• apache-servicemix-4.x.0-jbi : our current kit, builds on top of our basic assembly but adds NMR/JBI support plus all JBI components
• apache-servicemix-4.x.0-full : same configuration as the basic assembly, but this one has the bundles for all features in the system folder to facilitate offline deployment

Sub-Tasks

• Rename existing assembly to apache-servicemix-4.x.0-jbi: Resolved
• Add complete distribution for offline deployments: Resolved
• Add a basic distribution for new users: Resolved
• Add minimal distribution to allow building any ServiceMix-based distribution: Resolved