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

Full qualified names in "should be"s leads to compile errors #171

Open
borisbrodski opened this issue Sep 27, 2016 · 1 comment
Open

Full qualified names in "should be"s leads to compile errors #171

borisbrodski opened this issue Sep 27, 2016 · 1 comment

Comments

@borisbrodski
Copy link
Collaborator

fact "reproduce error" {
  java.lang.System => java.lang.System
}

generates

  @Test
  @Named("reproduce error")
  @Order(2)
  public void _reproduceError() throws Exception {
    Assert.assertTrue("\nExpected java.lang.System => java.lang.System but"
     + "\n     java.lang.System is " + new org.hamcrest.StringDescription().appendValue(System.class).toString()
     + "\n     java.lang is " + new org.hamcrest.StringDescription().appendValue(System.System).toString()
     + "\n     java is " + new org.hamcrest.StringDescription().appendValue(System).toString() + "\n", Should.operator_doubleArrow(
      System.class, System.class));

  }
riederm added a commit to riederm/Jnario that referenced this issue Apr 17, 2017
the JnarioCompiler no longer considers packageFragments as fully-fledged
sub-expressions
@riederm
Copy link

riederm commented Apr 17, 2017

Hi Boris,
I did a fix based on that still pending branch that moves xtext version to 2.11 and ports Xtend-Richstring to back to jnario.

Now I'm not really shure where I should place my pull requests. master on this repository is atm miles away from your latest developments (noXtend_2.9-branch). Are we eventually merging stuff back to this repository's master?

to be honest, the branch this commit depends on, has no relevant changes for the fix itself. Its just that I find it not so easy to get a fully functional IDE for the old versions used in this repo's master.

Lets either bring your or @sebastianbenz master-branch to the newest state and then make our latest developments against master.

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

No branches or pull requests

2 participants