Issue Details (XML | Word | Printable)

Key: GALAXY-115
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Andrew Perepelytsya
Reporter: Andrew Perepelytsya
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Galaxy

Merge some Galaxy and Bootstrap cli properties for consistency

Created: 19/Feb/08 03:07 PM   Updated: 13/Aug/08 10:14 PM
Component/s: Integration: Mule 1, Integration: Mule 2, Mule NetBoot
Affects Version/s: 1.0-RC
Fix Version/s: 1.x Backlog

Time Tracking:
Not Specified

Labels:
User impact: Medium


 Description  « Hide
At the moment there is some duplication of the properties (for historical reasons, bootstrap was developed after the initial integration). So, e.g. Galaxy credentials are specified one way for GalaxyConfigurationBuilder: http://www.mulesource.org/display/GALAXY/Mule+1 , but differently for Mule Bootstrap: -M-Dgalaxy.username

These should be unified for consistency. E.g. using ad-hoc System properties could be the way to go, as it doesn't require hacking any startup script and is already used throughout the startup process in several places. Additionally, defaults can be used for credentials to simplify initial setup.



 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Ross Mason added a comment - 19/Feb/08 03:35 PM
This is fine Andrew, but we still need to be able to pass in properties into the GalaxyConfigurationBuilder. I think passing the properties in as VM params will also work for both Mule 1 and Mule 2 client

Andrew Perepelytsya added a comment - 19/Feb/08 03:41 PM
Another (now) inconsistent property is the Galaxy Atom URL.

I'm trying to keep the scope small here - not repeat ourselves only. I'm not happy with the -M-Dgalaxy.workspace=MyMule syntax either, and would like a simpler one. However, diverting from the Mule version of startup scripts is a maintenance burden. I would love to rework it to use a neat commons-cli interface, but this has to be done in Mule first.

I think the -props galaxy.properties is fine for now, but I'd like to maybe synchronize names (GCB can be run without Mule bootstrap) and also make it check for system properties first, so that Bootstrap + GCB case reuses properties from the command line.