Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 393446

Summary: editor no longer showing bracket matching
Product: [ECD] Orion Reporter: Susan McCourt <susan>
Component: EditorAssignee: Mark Macdonald <mamacdon>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: mamacdon
Version: 1.0   
Target Milestone: 2.0 M1   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Susan McCourt CLA 2012-11-02 13:40:02 EDT
If I click at an open bracket I no longer get the highlight for the matching bracket.  It's working on 1.0 (orionhub) but broken on the current builds.
Comment 1 Mark Macdonald CLA 2012-11-02 13:57:26 EDT
Some CSS files are not being imported correctly. I caused this while fixing bug 393093.

Specifically, the relative paths to the CSS files are wrong: they have an extra '../' segment. This slipped by unnoticed while I was testing, because the paths still resolved. They only fail later on at build time, because the build runs inside a deeper directory structure, so the extra '../' matters:

     [java] Optimizing (standard.keepLines) CSS file: /shared/eclipse/e4/orion/I201211012230/optimization/edit/edit.css
     [java] /shared/eclipse/e4/orion/I201211012230/optimization/edit/edit.css
     [java]   Cannot inline css import, skipping: ../../orion/textview/textview.css
     [java] /shared/eclipse/e4/orion/I201211012230/optimization/edit/edit.css
     [java]   Cannot inline css import, skipping: ../../orion/textview/rulers.css
     [java] /shared/eclipse/e4/orion/I201211012230/optimization/edit/edit.css
     [java]   Cannot inline css import, skipping: ../../orion/textview/annotations.css
     [java] /shared/eclipse/e4/orion/I201211012230/optimization/edit/edit.css
     [java]   Cannot inline css import, skipping: ../../orion/textview/tooltip.css
Comment 2 Mark Macdonald CLA 2012-11-02 13:58:35 EDT
http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=f8d420244c5c42e18cbb6793d523299cc18839e0

This should be fixed in the next build