| [mdt-papyrus.dev] New plug-ins required in dev workspace |
Hi, Team, I am attempting a rebase today, and it is a lot of work tracking down the new plug-in projects that are now required by projects I already have in my workspace. Tracing from the oep.views.modelexplorer plug-in, there are a few new Xtext integration plug-ins, ALF plug-ins, and who knows what else required. Discovering each successive link in the dependency chain is time-consuming, because every time I import a few additional projects from the Git repo, Eclipse takes several minutes to think about the new workspace line-up and to rebuild everything. I can't just import all of the projects in Git because I know that many of them are long since abandoned and don't even compile. It seems that almost every time I fetch and rebase (at least once a week), I go through the same routine. Are there PSFs somewhere that make it easy to just import into the workspace the Papyrus plug-in projects that we should all have open, including any that are new since the last fetch? If not, I respectfully suggest that somebody should create PSFs for:
and it should be project policy that whenever new projects are added that are required by the projects already in one of these PSFs, those new projects are added to the PSF in the same commit. And when new projects are integrated into any of the features that we build and publish, they are likewise added to the PSFs in the same commit. Thanks, Christian P.S. There are also projects that I can't afford to keep open all the time, e.g. the large number of oep.uml.textedit.* plug-ins, because when Eclipse builds them, Xtext changes files so that my Git workspace is not clean. This prevents rebasing. Can we fix this? |