Community
Participate
Working Groups
PSFs do not currently work from GIT. Bug 296082 suggests that the requisite support is RESOLVED FIXED in EGIT, but is it in SR1 or M1 or M2?
It's in an additional Project Set Provider. Bug 363102 raised to find out how to make it work.
I'm wondering if we should only work with Buckminster materialization files and forget the PSFs. It's a matter of deciding what must go to the target platform and what must go to the workspace. Probably, stable projects like Platform, EMF and UML should go the TP and more active projects like, Xtext, mwe, etc should go the workspace. Regards, Adolfo.
In principle the GIT PSFs should be identical to the CVS PSFs, except that we may want to restructure slightly. The CVS PSFs leave as much in plugins as possible, the notable exceptions were LPG, EMF Examples Library, UML Resources. With improved standalone startup, I'm most of the way to be being able to access UML Resources from a plugin, which would avoid having to get the whole of UML from GIT. EMF isn't yet in GIT so EMF Examples Library is easy. The main problem to total UML Resources from a plugin is that org.eclipse.ocl.examples.domain.utilities.StandaloneProjectMap needs to be accessed by the UML tests. It may be appropriate to introduce an org.eclipse.ocl.common plugin for stable functionality shared by but independent of Ecore/UML/Pivot.
(In reply to comment #3) > The main problem to total UML Resources from a plugin is that > org.eclipse.ocl.examples.domain.utilities.StandaloneProjectMap needs to be > accessed by the UML tests. I think this has been fixed by doing a classpath search. (In reply to comment #2) > I'm wondering if we should only work with Buckminster materialization files > and forget the PSFs. I'm not quite sure what this means for the user. We need to provide clear instructions to the user on how to get useable sources. Ideally a single menu activation like Import Project Set Z.psf. But a two step would do: a) clone the repo (importing nothing) b) use facility X with Z.X to import the category Z plugins Does Buckminster provide something like this?
(In reply to comment #3) > In principle the GIT PSFs should be identical to the CVS PSFs, except that > we may want to restructure slightly. GIT PSFs now work, but since they clone the entire repo, the partial PSFs are not very helpful. Therefore a single import-all PSF partitioned into Working Sets to facilitate user pruning.
CLOSED after more than a year in RESOLVED state.
and CLOSE
