Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


miryamgsm last won the day on February 17 2014

miryamgsm had the most liked content!

Community Reputation

2 Neutral

About miryamgsm

  • Rank
    Advanced Member

Recent Profile Visitors

24,792 profile views
  1. Yes, we're working to include more functionality in the new plugin but you can use both plugins at the same time Best regards, Míryam
  2. We will take into account your suggestions for future improvements. Thanks for your feedback. Best regards, Míryam
  3. I reviewed the source code of the SemanticMerge application and the pas2yaml parser. The 'end' string is only sent when SemanticMerge is launched through our version control tools (Plastic SCM and gmaster). If I am correct, I think the "Exception Exiting because INPUT reached EOF" exception occurs when you close SemanticMerge due the process is not closed correctly using the 'end' string. We will fix it as soon as possible. Meanwhile, you probably could workaround the issue avoid throwing the exception. Does it sound good for you? We will keep you informed as soon as it is ready! Thanks for your feedback. Best regards, Míryam
  4. Hi dummzeuch! * I think it's better to try the parser step by step in order to determine the origin of the problem. That is, first only the parser then the integration with SemanticMerge and finally with Tortoise svn. To check only the parser: yourparserapplication.exe shell path_to_the_flag_file More info: https://users.semanticmerge.com/documentation/external-parsers/external-parsers-guide.shtml#Asampleparsingsession To check the integration with SemanticMerge: semanticmergetool.exe -s sample\source.code -d sample\destination.code -ep=codeparser.exe More info: https://users.semanticmerge.com/documentation/external-parsers/external-parsers-guide.shtml#SemanticMergeandSemanticDiff * Sometimes, issues will happen if you forget to fill in the declarations tree correctly. If that happens, besides checking the error messages, looking at the logs might be very useful. In this section, you can find the steps to activate the "ExternalParser" logging: https://users.semanticmerge.com/documentation/external-parsers/external-parsers-guide.shtml#Howtodebugyourparser Tip: Maybe you can start with simplified source code, check it and, once it works, add the rest of the code. In case the issue is not solved, you can share with us the parser in order to debug the SemanticMerge application to figure out what is happens. Please do not hesitate to contact us if you have any questions. Hope it helps! Best regards, Míryam
  5. Hi @Jason H, Happy to announce a new release of SemanticMerge! It includes the fix for your reported issue related to the svg assembly. https://users.semanticmerge.com/releasenotes/ Thanks again for all your great feedback. Best regards, Míryam
  6. Hi all, A new release of Plastic/Jenkins plugin with the 'lightweight checkout' feature is already available (2.13). https://plugins.jenkins.io/plasticscm-plugin Thanks for the report. Best regards, Míryam
  7. Not at all. Thanks again for your great feedback Best regards, Míryam
  8. Hi Mikael, Sorry for the inconveniences and thank you for your feedback. Regarding the issues, Issue 1: The changeset number is not filled/drawn in the GUI. * I am able to reproduce the issue with a git repo. * It is a bug in the Blue Ocean plugin: https://issues.jenkins-ci.org/browse/JENKINS-46521 Issue 2: If a build includes multiple changesets, it will only render one of them when clicking in the detail. * The next release will contain the fix. Best regards, Míryam
  9. Hi! Thank you for your feedback! We'll release a fix as soon as possible. Regarding the splitter preview problem, it's a well-known issue caused by having WPF and WinForms controls at the same time. We intend to port the whole application to WPF in the future, which will make the problem disappear. Sorry for the inconveniences. Best regards, Míryam
  10. Perfect! Regarding the license, you need a specific license for external language if you want to save the result file. Please do not hesitate to contact us for anything you may need. Best regards, Míryam
  11. Hi Gerard, It sounds good! The name of the declaration (container or terminal node) is required but you can set a default value. SemanticMerge uses this field for two purposes: * identify the declaration and show it on GUI. * improve the matching declaration process; it tries to match declarations with the same name (of course, they must be the same type), otherwise it tries by similitude. In other words, when you specify the name of the declarations you make the matching process easier but this is not always possible. Please, write us if you need a trial license for the external languages Best regards, Míryam
  12. Hi Dan, It works fine on my windows 7 box and my windows 8 box. Could you review if you have any differences? What is your operative system? When do you reproduce the bug, always or in special circumstance? Thanks in advance. Best regards, Míryam
  13. Great! Thanks for your kind cooperation. Regards, Míryam
  14. Hi! Usually, you can perform this option through the control version system. Anyway, please add your suggestion to the uservoice forum to share it with the other users! The uservoice forum is here: http://plasticscm.uservoice.com/forums/196398-mergebegins Best regards, Míryam
  15. Hi Michel, Your suggestion is really interesting, it was added to our roadmap. Please, could you include your suggestion to the uservoice forum to share it with the other users? The uservoice forum is here: http://plasticscm.uservoice.com/forums/196398-mergebegins Best regards, Míryam
  • Create New...