[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [qvto-dev] Project Sets
|
Hi
I'm dispassionate, so deleting the Project Sets is fine with me.
Regards
Christopher
-----Ursprüngliche Nachricht-----
Von: qvto-dev-bounces@xxxxxxxxxxx [mailto:qvto-dev-bounces@xxxxxxxxxxx] Im Auftrag von Ed Willink
Gesendet: Dienstag, 31. Oktober 2017 13:11
An: QVTOML developer mailing list <qvto-dev@xxxxxxxxxxx>
Betreff: [qvto-dev] Project Sets
Hi
I was updating the QVTo PMI and came across references to Project Sets, so I started updating them and then tested them.
They seem to be just as useless to active developers as OOMPH; at least Importing a Project Set fails, after a few minutes loading a new GIT, whereas OOMPH merrily gives you a duplication from which it takes a few days to unwind all the obscure losses of completion assist, wrong target, ...
A new developer might be better off with OOMPH than Import Project Set.
An old developer must not use either.
I suggest that the Project Sets are deleted.
Comments?
Regards
Ed Willink
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
qvto-dev mailing list
qvto-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/qvto-dev
