Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Refactoring Specification (Buckminster)
Revision as of 08:57, 5 December 2006 by Unnamed Poltroon (Talk)
Right now, this specification only contains some ideas regarding Refactoring that Buckminster could support:
From direct dependencies to a configuration component
Sometimes a component dependencies evolve to a state where its dependencies are useful for other components. I.e. when creating component B, it has the same (or a large overlapping) set of dependencies with component A previously created. An action to take (rather than just copying CSPEC from component A to component B and changing the A specifics) it would be better to aid the user in creating a configuration component that both A and B can depend on.
This refactoring would aid the user with:
- creating a configuration component (C)
- copying and transforming the CSPEC in A to a CSPEC in C with all A specifics pruned
- modifying A's CSPEC to prune all the dependencies now in C, and adding the dependency to C
This could be a implemented as a Wizard.