Bug 472803 - AQL completion can produce messages in the console/stdout
Summary: AQL completion can produce messages in the console/stdout
Status: RESOLVED FIXED
Alias: None
Product: Acceleo
Classification: Modeling
Component: Query Language (show other bugs)
Version: 3.6.0   Edit
Hardware: All All
: P3 minor
Target Milestone: ---   Edit
Assignee: Yvan Lussaud CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 470460
  Show dependency tree
 
Reported: 2015-07-16 05:21 EDT by Pierre-Charles David CLA
Modified: 2015-08-31 05:56 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre-Charles David CLA 2015-07-16 05:21:07 EDT 
Steps to reproduce (using Sirius, but the problem is more general):
1. Start an Eclipse either from the shell/console, or as a runtime
2. Open the "Interpreter" view, and select "Sirius Interpreter" as language
3. Open a Sirius representation and select an element
4. In the interpreter view, type "aql:self." and hit Ctrl+space to trigger auto-completion

The completion works fine, but in the terminal or console from where the Eclipse was launched, messages appear which look like they were produced by the internal ANTLR parser:

line 1:5 no viable alternative at input '.'
line 1:5 no viable alternative at input '.'
Comment 1 Pierre-Charles David CLA 2015-07-16 05:23:44 EDT 
Forgot to mention: this is using AQL 3.6.0.201506080954.
Comment 2 Yvan Lussaud CLA 2015-07-24 03:13:30 EDT 
This has been fixed in previous commits by modifying QueryBuilderEngine.build(String):
 - adding parser.removeErrorListeners(); Commit a4c20d670351486ef4f4fb18d0cd12115fd61ae6
 - removing parser.setTrace(true); Commit ec43354ad620b8354ef772698b12c1fb517b68ab

This messages will not show ups with next builds.
Comment 3 Cedric Brun CLA 2015-08-31 05:56:42 EDT 
Fixed