use super-project to group related separate projects
Several customers have a setting where they have a huge application that is split in several projects that are referring to each other. The requirements are that it should be possible to navigate code from one project to another, even if the destination project is not present in the current workspace.
This has been handled by using external_modules references, but the result is confusing: a module is present in the "externals" of all other projects and also in its own project; when navigating to it, the editor is open on a target that depends on there the navigation started and the status of the module's project (open/closed). This is weird for both users and developers that have to keep track of that.
The suggestion is to use a super-project similar to a feature project in PDE, that knows what all the application's projects are and when we are required to navigate to a file not present in the workspace, the right project can be opened automatically and the right file is shown in the editor.
This has been handled by using external_modules references, but the result is confusing: a module is present in the "externals" of all other projects and also in its own project; when navigating to it, the editor is open on a target that depends on there the navigation started and the status of the module's project (open/closed). This is weird for both users and developers that have to keep track of that.
The suggestion is to use a super-project similar to a feature project in PDE, that knows what all the application's projects are and when we are required to navigate to a file not present in the workspace, the right project can be opened automatically and the right file is shown in the editor.
Leave a comment
on 2011-08-24 13:18 *
By Vlad Dumitrescu
Updating tickets (#802, #52, #64, #460, #720, #749, #769, #775, #776, #786, #851, #83, #93, #149, #157, #163, #179, #194, #195, #222, #228, #274, #281, #283, #285, #335, #339, #349, #351, #358, #364, #373, #375, #379, #383, #401, #405, #409, #411, #413, #422, #424, #425, #428, #434, #442, #443, #449, #450, #454, #471, #479, #492, #523, #535, #537, #543, #561, #564, #574, #590, #598, #599, #603, #610, #615, #619, #632, #634, #636, #639, #640, #641, #642, #643, #645, #658, #660, #662, #664, #665, #674, #677, #684, #685, #688, #689, #693, #694, #695, #696, #699, #700, #707, #709, #719, #736, #743, #744, #746, #748, #759, #760, #761, #762, #774, #778, #780, #788, #789, #796, #798, #799, #800, #803, #809, #812, #813, #816, #820, #822, #829, #836, #837, #840, #841, #842, #848, #849, #850, #853, #854, #855, #856, #857, #860, #867, #868, #871, #872, #873, #875, #41, #159, #372, #429, #489, #577, #601, #622, #667, #679, #767, #768, #772, #785, #771)
on 2011-09-27 15:12 *
By Vlad Dumitrescu
Component changed from None to project model
Component changed from None to project model
on 2014-11-01 00:51 *
By Vlad Dumitrescu
Status changed from New to Invalid
Status changed from New to Invalid
no, it's a completely new thing, not eclipse-like. let's keep to the way all eclipse works.
working sets are similar to this idea.
working sets are similar to this idea.