[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [qvto-dev] Bugs found during unparser development
|
Hi,
Sergey, I decided to make my tests resilient against whether
MappingCallExp.setOperationCode() gets updated or not.
A git patch containing the implementation of
QvtOperationsResourceImpl.doSave()
as well as accompanying junit tests is attached to the original bug
report 377320.
The tests use org.eclipse.compare now, instead of EMFCompare.
I signed the CLA a couple of weeks ago.
Please advise on what remains for me to do to bring 377320 to a close.
Best Regards
Uwe
Am 06.03.2016 um 14:40 schrieb Uwe Ritzmann:
Dear QVTo enthusiasts,
as promised I started to file bugs for the issues I found during
development of the QVTo unparser:
489093 MappingCallExp.setOperationCode() not called in
QvtOperationalVisitorCS.createMappingCallExp()
489092 Helper.isQuery not set by QvtOperationalVisitorCS.java
These bugs do not encumber my unparser, but as it will, besides other
uses, enable qvto-to-qvto-Transformations,
it would be beneficial for the users if the AST from the parser is as
correct to the original source as possible.
Best Regards
Uwe
_______________________________________________
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
