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.

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

ConfigurationOfMoose should be split to reflect core vs suite #853

Closed
seandenigris opened this issue Aug 3, 2015 · 2 comments
Closed

ConfigurationOfMoose should be split to reflect core vs suite #853

seandenigris opened this issue Aug 3, 2015 · 2 comments

Comments

@seandenigris
Copy link
Contributor

Originally reported on Google Code with ID 853

Right now, in ConfigurationOfMoose we have two methods:
- coreDefault
- default

These should be the basis for splitting into two distinct configuration classes.

Ideally, we would rename ConfigurationOfMoose to ConfigurationOfMooseSuite, but this
is difficult due to the many scripts that depend on the current name. So, we will not
do that (at least not now).

Also, in the process of splitting, we will remove the 'default' version and transform
it into a baseline.

Reported by tudor@tudorgirba.com on 2012-10-15 06:23:27
@seandenigris
Copy link
Contributor Author

Reported by tudor@tudorgirba.com on 2013-01-27 08:21:46

  • Labels added: Milestone-4.8
  • Labels removed: Milestone-4.7

@seandenigris
Copy link
Contributor Author 

The configuration was refactored in a different way. We now have a baseline and we use
#development.

It would still be good to have groups for engine projects, but this is for another
time.

Reported by tudor@tudorgirba.com on 2013-07-02 09:38:21

  • Status changed: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@seandenigris