org.eclipse.xtext.formatting2.internal.RegionTrace

newLine=2

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web2

  • newLine=2
  • Stack trace

    • org.eclipse.xtext.formatting2.internal.RegionTrace: newLine=2 at org.eclipse.xtext.formatting2.internal.ArrayListTextSegmentSet.insertAtIndex(ArrayListTextSegmentSet.java:78) at org.eclipse.xtext.formatting2.internal.ArrayListTextSegmentSet.add(ArrayListTextSegmentSet.java:45) at org.eclipse.xtext.formatting2.internal.FormattableDocument.addReplacer(FormattableDocument.java:73) at org.eclipse.xtext.formatting2.internal.FormattableDocument.set(FormattableDocument.java:310) at org.eclipse.xtext.formatting2.internal.FormattableDocument.append(FormattableDocument.java:83) at org.eclipse.xtend.core.formatting2.XtendFormatter._format(XtendFormatter.java:129) Caused by: org.eclipse.xtext.formatting2.ConflictingFormattingException: Conflicting values for 'newLineMin': '2' and '1'. at org.eclipse.xtext.formatting2.internal.HiddenRegionFormatting.merge(HiddenRegionFormatting.java:102) at org.eclipse.xtext.formatting2.internal.HiddenRegionFormatting.mergeValuesFrom(HiddenRegionFormatting.java:111) at org.eclipse.xtext.formatting2.internal.HiddenRegionFormattingMerger.merge(HiddenRegionFormattingMerger.java:32) at org.eclipse.xtext.formatting2.internal.HiddenRegionFormattingMerger.merge(HiddenRegionFormattingMerger.java:1) at org.eclipse.xtext.formatting2.internal.TextReplacerMerger.mergeHiddenRegionReplacers(TextReplacerMerger.java:73) at org.eclipse.xtext.formatting2.internal.TextReplacerMerger.merge(TextReplacerMerger.java:36) at org.eclipse.xtext.formatting2.internal.TextReplacerMerger.merge(TextReplacerMerger.java:1) at org.eclipse.xtext.formatting2.internal.ArrayListTextSegmentSet.replaceExistingEntry(ArrayListTextSegmentSet.java:120) ... 6 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.