[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mdt-papyrus.dev] Deprecated folder in repository
|
Hi Andrew,
In theory, everything you need is in the plugins/ folder, and EGit supports recursive project import (So, import all projects from plugins/, and you're done). That's better than a PSF, because the PSF needs to be updated, whereas "Import from plugins" is always up-to-date (Which is why we deprecated the PSF container: not useful anymore).
That's "in theory", because there's still the developer/ folder which is located in the plugins/ folder, as well as a few un-released plug-ins which made their way out of sandbox a little bit too early. But, well, that's exactly why we need to clean the repo :)
Regards,
Camille
__________________________
Camille Letavernier
+33 (0)1 69 08 00 59 - camille.letavernier@xxxxxx
CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE)
Papyrus : http://www.eclipse.org/papyrus
-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Andrew Eidsness
Envoyé : vendredi 4 avril 2014 14:51
À : mdt-papyrus.dev@xxxxxxxxxxx
Objet : Re: [mdt-papyrus.dev] Deprecated folder in repository
As someone that fits into the "outsider" category I agree with this.
The particular problem I had was importing projects with EGit's "Import Projects" wizard. I imported based on the project name that I knew was needed and didn't notice that I had accidentally selected versions from the "sandbox"
folder, when I actually needed copies from elsewhere in the tree.
I don't think that deleting old projects matters as much, but from a new-developer perspective it would be really helpful to have a Team Project Set available somewhere -- perhaps in the releng folder.
-Andrew
On 14-04-04 08:10 AM, WOUTERS Laurent wrote:
> Hello all,
>
>
>
> I am pondering the use of the folder named 'deprecated' in the source
> tree. As I understand, plugins and features that are no longer part of
> the build are moved to this folder, and this is neither automatic, nor
> systematic because lots of plugins in the 'plugins' folder are not part of any build (main and extra). I am aware than some of them are meant for the Papyrus developers.
>
>
>
> Still, I am under the impression that this creates some confusion and
> noise when looking at the source tree from an outsider perspective. I
> believe the standard practice would be to simply delete the deprecated
> bundles when they are removed from the build. It is always possible to go back in the history to look at and retrieve the code. Furthermore, to ease this process we can tag the commit that removed the bundle with a name of a particular form, e.g. "last/<bundleID>".
>
> Do you have any thoughts on that ?
>
>
>
> Regards,
>
> Laurent
>
>
>
> _______________________________________________
> mdt-papyrus.dev mailing list
> mdt-papyrus.dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
>
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
