Bug 1129414
| Summary: | DR1's switchyard-2.0.0.Alpha1-redhat-1-features.xml could lead to users unintentionally deploying quickstarts to production server | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | SwitchYard | Assignee: | tcunning |
| Status: | NEW --- | QA Contact: | Matej Melko <mmelko> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | soa-p-jira |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Having a separate features.xml for the quickstarts is probably not a bad idea. One per quickstart might be too granular. Won't production users install via the profiles we distribute with the product? |
Description of problem: The switchyard-2.0.0.Alpha1-redhat-1-features.xml file in the DR1 build includes references to the switchyard quickstarts - for example: <feature name="switchyard-quickstart-camel-bindy" version="2.0.0.Alpha1-redhat-1" resolver="(obr)"> <feature version="2.0.0.Alpha1-redhat-1">switchyard-bean</feature> <feature version="2.0.0.Alpha1-redhat-1">switchyard-file</feature> <feature version="2.12.0.redhat-610379">camel-bindy</feature> <bundle>mvn:org.switchyard.quickstarts/switchyard-camel-bindy/2.0.0.Alpha1-redhat-1</bundle> </feature> Do we want to retain this approach - or change it to a model where each quickstart app includes it own features.xml file? It seems like each if quickstart was packaged with a features.xml file would be make for a better approach so that users could more easily copy/extend a quickstart into a customer app. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: