Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content Assist crashes when a resource is indicated with variable file (1.1.0) #48

Open
bgd77 opened this issue Feb 26, 2013 · 1 comment
Labels

Comments

@bgd77
Copy link

bgd77 commented Feb 26, 2013

This happens on version 1.1.0.

I indicate the path to some resources by using the following expression:
"Resource ${RESOURCES}/user-keywords.txt"

The ${RESOURCES} variable is created in the Robot Framework Maven Plugin as a variable:
"RESOURCES:${project.basedir}/resources"

When I try to use the content assist in a test file that contains that type of resource import mentioned at the beginning the following error is displayed:

"Content Assist" did not complete normally. Please see the log for more information.
Relative path in absolute URI: file:D:/...path_to_project.../robot/src/main/scenarios/$%7BRESOURCES%7D/user-keywords.txt

This path is incorrect, it should be:
D:/...path_to_project.../robot/resources/user-keywords.txt
because "robot" is the base directory of the project.

@xkr47
Copy link
Member

xkr47 commented Feb 26, 2013

Since the plugin does not currently understand maven plugin configurations, it will not know of variables declared there. So it will not know where to look for the user-keywords.txt. The path it tries to look for is indeed incorrect; if it cannot resolve the file, it should just ignore it.

Supporting maven plugin configurations is one option, but I think the first step towards that goal would be to allow declaring run-time variables in the Project or workspace preferences. There you could then define RESOURCES to match the maven configuration and the editor would be able to understand where to look for the file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants