Issue 853 in moose-technology: ConfigurationOfMoose should be split to reflect core vs suite
Status: New Owner: ---- Labels: Type-Engineering Priority-Medium Milestone-4.7
New issue 853 by tu...@tudorgirba.com: ConfigurationOfMoose should be split to reflect core vs suite http://code.google.com/p/moose-technology/issues/detail?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.
Updates: Labels: -Milestone-4.7 Milestone-4.8
Comment #1 on issue 853 by tu...@tudorgirba.com: ConfigurationOfMoose should be split to reflect core vs suite http://code.google.com/p/moose-technology/issues/detail?id=853
(No comment was entered for this change.)
Updates: Status: Fixed
Comment #2 on issue 853 by tu...@tudorgirba.com: ConfigurationOfMoose should be split to reflect core vs suite http://code.google.com/p/moose-technology/issues/detail?id=853
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.
-
moose-technology＠googlecode.com