Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Generalize how configuration variables are set #7

Open
GoogleCodeExporter opened this issue Jul 24, 2015 · 0 comments
Open

Generalize how configuration variables are set #7

GoogleCodeExporter opened this issue Jul 24, 2015 · 0 comments
Labels
auto-migrated Module-cwm-data Priority-Low Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

Right now cwm-data (and perhaps other modules) expect certain settings to be 
accessed via a properties file.  Consider moving to a more general system where 
there is a Configuration object, and filling it from a properties file is just 
one option.

Original issue reported on code.google.com by [email protected] on 1 Sep 2011 at 3:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Module-cwm-data Priority-Low Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter