Priority: To be reviewed
Resolution: Won't Fix or Usage Issue
Affects Version/s: 3.1.1
Fix Version/s: None
Component/s: Examples / Tutorials
MULE-5517 Example Launcher requires JAVA_HOME to be set MULE-5453 Create a wiki page for the examples launcher MULE-5771 Mule examples launcher fails to build with maven MULE-3550 loanbroker bpm example's config is invalid MULE-5708 In the example-launcher example. link in the README.txt points to a page which says "You cannot view this page due to inherited restrictions" MULE-5425 Mule example launcher: instructions to run are incorrect MULE-2514 ErrorHandler example has invalid XML config MULE-6255 Mule example launcher is not working MULE-3704 AttachmentsPropagationTestCase needs XML config file MULE-5714 Running mvn on example launcher generates mule-example-launcher.zip (no version) in the apps directory.
The examples launcher is nice but has not been designed with maintenance in mind:
- There is an independent copy (i.e., fork) of the XML config for each example. This will quickly become a maintenance nightmare.
- The "about" page contains info. which already is or should be in the README.txt for each example.
- The "run" page (HTML front-end) for each example really belongs in the example itself, not in the launcher.
Ideally, the launcher should just be a container which displays the above info. from each example. We need to refactor things a bit so that the XML, README, and UI for each example live (and are maintained) inside the example itself and are merely consolidated and presented by the launcher.
|Assignee||Mariano Capurro [ mariano.capurro ]|
|Workflow||Fixed Main Mule Workflow (after JIRA upgrade) [ 81273 ]||Main Mule Workflow v1.0 [ 135323 ]|
|Resolution||Won't Fix or Usage Issue [ 2 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1085d 6h 30m||1||Alejandro Sequeira||17/Mar/14 02:30 PM|